Replaced dropped cross-references (#2034)

* Replaced dropped cross-references

* add missing para tag

Author: Ron Petrusha

xml/System.Resources/MissingManifestResourceException.xml

@@ -58,7 +58,7 @@
   
 -   The resource set is not identified by its fully qualified name. For example, if the `baseName` parameter in the call to the <xref:System.Resources.ResourceManager.%23ctor%28System.String%2CSystem.Reflection.Assembly%29?displayProperty=nameWithType> method specifies the root name of the resource set without a namespace, but the resource set is assigned a namespace when it is stored in its assembly, the call to the <xref:System.Resources.ResourceManager.GetString%2A?displayProperty=nameWithType> method throws this exception.  
   
-     If you have embedded the .resources file that contains the default culture's resources in your executable and your app is throwing a <xref:System.Resources.MissingManifestResourceException>, you can use a reflection tool such as  to determine the fully qualified name of the resource. In ILDasm, double click the executable's **MANIFEST** label to open the **MANIFEST** window. Resources appear as `.mresource` items and are listed after external assembly references and custom assembly-level attributes. You can also compile the following simple utility, which lists the fully qualified names of embedded resources in the assembly whose name is passed to it as a command-line parameter.  
+     If you have embedded the .resources file that contains the default culture's resources in your executable and your app is throwing a <xref:System.Resources.MissingManifestResourceException>, you can use a reflection tool such as the [IL Disassembler (Ildasm.exe)](~/docs/framework/tools/ildasm-exe-il-disassembler.md) to determine the fully qualified name of the resource. In ILDasm, double click the executable's **MANIFEST** label to open the **MANIFEST** window. Resources appear as `.mresource` items and are listed after external assembly references and custom assembly-level attributes. You can also compile the following simple utility, which lists the fully qualified names of embedded resources in the assembly whose name is passed to it as a command-line parameter.  
   
      [!code-csharp[System.Resources.ResourceManager.Class#4](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.resources.resourcemanager.class/cs/resourcenames.cs#4)]
      [!code-vb[System.Resources.ResourceManager.Class#4](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.resources.resourcemanager.class/vb/resourcenames.vb#4)]  

xml/System.Resources/ResXResourceReader.xml

@@ -506,9 +506,7 @@
         </remarks>
         <block subset="none" type="overrides">
           <para>
-            <see langword="Dispose" /> can be called multiple times by other objects. When overriding <see langword="Dispose(Boolean)" />, be careful not to reference objects that have been previously disposed of in an earlier call to <see langword="Dispose" />. For more information about how to implement <see langword="Dispose(Boolean)" />, see [Implementing a Dispose Method](~/docs/standard/garbage-collection/implementing-dispose.md).  
-  
- For more information about <see langword="Dispose" /> and <see cref="M:System.Object.Finalize" />, see  and .</para>
+            <see langword="Dispose" /> can be called multiple times by other objects. When overriding <see langword="Dispose(Boolean)" />, be careful not to reference objects that have been previously disposed of in an earlier call to <see langword="Dispose" />. For more information about how to implement <see langword="Dispose(Boolean)" /> and about the disposable pattern, see [Implementing a Dispose Method](~/docs/standard/garbage-collection/implementing-dispose.md), <see cref="T:System.IDisposable" />, and <see cref="M:System.Object.Finalize" />.</para>
         </block>
       </Docs>
     </Member>
@@ -867,4 +865,4 @@
       </Docs>
     </Member>
   </Members>
-</Type>
+</Type>

xml/System.Security/SecurityException.xml

@@ -735,7 +735,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property contains the denied permission, permission set, or permission set collection that caused the security check to fail. It is `null` for exceptions that are not caused by a Deny. The property is of type <xref:System.Object> because it can contain a permission, a permission set, or a permission set collection. To test the run-time type of this property, you can use the <xref:System.Object.GetType%2A> method or a specific language operator, such as the  operator in C# or the  operator in Visual Basic.  
+ This property contains the denied permission, permission set, or permission set collection that caused the security check to fail. It is `null` for exceptions that are not caused by a Deny. The property is of type <xref:System.Object> because it can contain a permission, a permission set, or a permission set collection. To test the run-time type of this property, you can use the <xref:System.Object.GetType%2A?displayProperty=nameWithType> method or a specific language operator, such as the [is operator](~/docs/csharp/language-reference/keywords/is.md) in C# or the [TypeOf operator](~/docs/visual-basic/language-reference/operators/typeof-operator.md) in Visual Basic.  
   
  ]]></format>
         </remarks>
@@ -1141,7 +1141,7 @@
 ## Remarks  
  The <xref:System.Security.SecurityException.PermitOnlySetInstance%2A> property represents the permitted permission, permission set, or permission set collection contained in the stack frame that caused the security exception. For instance, when a security exception occurs because of a <xref:System.Security.PermissionSet.Demand%2A?displayProperty=nameWithType> failure, the permitted permission appears in this property and the demanded <xref:System.Security.PermissionSet> is contained in the <xref:System.Security.SecurityException.Demanded%2A> property.  
   
- This property is of type <xref:System.Object> because permissions, permission sets, or permission set collections can all be demanded and <xref:System.Object> is their common base class.  To test the run-time type of this property, you can use the <xref:System.Object.GetType%2A> method or a specific language operator, such as the  operator in C# or the  operator in Visual Basic.  
+ This property is of type <xref:System.Object> because permissions, permission sets, or permission set collections can all be demanded and <xref:System.Object> is their common base class.  To test the run-time type of this property, you can use the <xref:System.Object.GetType%2A> method or a specific language operator, such as the [is operator](~/docs/csharp/language-reference/keywords/is.md) in C# or the [TypeOf operator](~/docs/visual-basic/language-reference/operators/typeof-operator.md) in Visual Basic.  
   
  ]]></format>
         </remarks>