[NFC][RemoveDIs] Fix some comments in DebugProgramInstruction.h

llvm/include/llvm/IR/DebugProgramInstruction.h

@@ -32,9 +32,8 @@
 // ; }
 // ;; There is a debug-info record in front of the %bar instruction,
 // ;; thus it points at a DbgMarker object. That DbgMarker contains a
-// ;; DbgVariableRecord in it's ilist, storing the equivalent information
-// to the
-// ;; dbg.value above: the Value, DILocalVariable, etc.
+// ;; DbgVariableRecord in its ilist, storing the equivalent information
+// ;; to the dbg.value above: the Value, DILocalVariable, etc.
 //
 // This structure separates the two concerns of the position of the debug-info
 // in the function, and the Value that it refers to. It also creates a new
@@ -121,7 +120,7 @@ template <typename T> class DbgRecordParamRef {
 /// within IR. Features various methods copied across from the Instruction
 /// class to aid ease-of-use. DbgRecords should always be linked into a
 /// DbgMarker's StoredDbgRecords list. The marker connects a DbgRecord back to
-/// it's position in the BasicBlock.
+/// its position in the BasicBlock.
 ///
 /// We need a discriminator for dyn/isa casts. In order to avoid paying for a
 /// vtable for "virtual" functions too, subclasses must add a new discriminator
@@ -272,9 +271,8 @@ class DbgVariableRecord : public DbgRecord, protected DebugValueUser {
  Any, ///< To indicate all LocationTypes in searches.
  };
  /// Classification of the debug-info record that this DbgVariableRecord
- /// represents. Essentially, "is this a dbg.value or dbg.declare?".
- /// dbg.declares are not currently supported, but it would be trivial to do
- /// so.
+ /// represents. Essentially, "does this correspond to a dbg.value,
+ /// dbg.declare, or dbg.assign?".
  /// FIXME: We could use spare padding bits from DbgRecord for this.
  LocationType Type;