remove weird tagging (#4515)

mairaw · web-flow · commit 84138569e9a7 · 2020-07-14T14:40:21.000-07:00
diff --git a/xml/Microsoft.VisualBasic/Collection.xml b/xml/Microsoft.VisualBasic/Collection.xml
@@ -896,8 +896,7 @@ MsgBox(CStr(customers(1)))
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [Visual Basic, C#]  
-  
+
  The `foreach` statement of the C# language (`for each` in Visual Basic) hides the complexity of the enumerators. Therefore, using `foreach` is recommended, instead of directly manipulating the enumerator.  
   
  Enumerators can be used to read the data in the collection, but they cannot be used to modify the underlying collection.  
diff --git a/xml/System.Collections.Specialized/IOrderedDictionary.xml b/xml/System.Collections.Specialized/IOrderedDictionary.xml
@@ -120,8 +120,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [Visual Basic, C#]  
-  
+
  The `foreach` statement of the C# language (`for each` in Visual Basic) hides the complexity of the enumerators.  Therefore, using `foreach` is recommended instead of directly manipulating the enumerator.  
   
  Enumerators can be used to read the data in the collection, but they cannot be used to modify the underlying collection.  
diff --git a/xml/System.Collections.Specialized/OrderedDictionary.xml b/xml/System.Collections.Specialized/OrderedDictionary.xml
@@ -749,8 +749,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [Visual Basic, C#]  
-  
+
  The `foreach` statement of the C# language (`for each` in Visual Basic) hides the complexity of the enumerators.  Therefore, using `foreach` is recommended instead of directly manipulating the enumerator.  
   
  Enumerators can be used to read the data in the collection, but they cannot be used to modify the underlying collection.  
diff --git a/xml/System.Collections.Specialized/StringCollection.xml b/xml/System.Collections.Specialized/StringCollection.xml
@@ -547,8 +547,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [Visual Basic, C#]  
-  
+
  The `foreach` statement of the C# language (`for each` in Visual Basic) hides the complexity of the enumerators.  Therefore, using `foreach` is recommended, instead of directly manipulating the enumerator.  
   
  Enumerators can be used to read the data in the collection, but they cannot be used to modify the underlying collection.  
@@ -1189,8 +1188,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [Visual Basic, C#]  
-  
+
  The `foreach` statement of the C# language (`for each` in Visual Basic) hides the complexity of the enumerators.  Therefore, using `foreach` is recommended, instead of directly manipulating the enumerator.  
   
  Enumerators can be used to read the data in the collection, but they cannot be used to modify the underlying collection.  
diff --git a/xml/System.Collections/CollectionBase.xml b/xml/System.Collections/CollectionBase.xml
@@ -404,8 +404,7 @@ A <xref:System.Collections.CollectionBase> instance is always modifiable. See <x
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [Visual Basic, C#]  
-  
+   
  The `foreach` statement of the C# language (`for each` in Visual Basic) hides the complexity of the enumerators.  Therefore, using `foreach` is recommended, instead of directly manipulating the enumerator.  
   
  Enumerators can be used to read the data in the collection, but they cannot be used to modify the underlying collection.  
diff --git a/xml/System.Collections/Hashtable.xml b/xml/System.Collections/Hashtable.xml
@@ -2289,7 +2289,6 @@ Each element is a key/value pair stored in a <xref:System.Collections.Dictionary
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [Visual Basic, C#]  
   
  The `foreach` statement of the C# language (`for each` in Visual Basic) hides the complexity of the enumerators.  Therefore, using `foreach` is recommended, instead of directly manipulating the enumerator.  
   
@@ -3259,7 +3258,6 @@ Each element is a key/value pair stored in a <xref:System.Collections.Dictionary
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [Visual Basic, C#]  
   
  The `foreach` statement of the C# language (`for each` in Visual Basic) hides the complexity of the enumerators.  Therefore, using `foreach` is recommended, instead of directly manipulating the enumerator.  
   
diff --git a/xml/System.Collections/IDictionary.xml b/xml/System.Collections/IDictionary.xml
@@ -316,8 +316,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [Visual Basic, C#]  
-  
+
  The `foreach` statement of the C# language (`for each` in Visual Basic) hides the complexity of the enumerators.  Therefore, using `foreach` is recommended instead of directly manipulating the enumerator.  
   
  Enumerators can be used to read the data in the collection, but they cannot be used to modify the underlying collection.  
diff --git a/xml/System.Collections/SortedList.xml b/xml/System.Collections/SortedList.xml
@@ -2316,8 +2316,7 @@ A <xref:System.Collections.SortedList> element can be accessed by its key, like
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [Visual Basic, C#]  
-  
+
  The `foreach` statement of the C# language (`for each` in Visual Basic) hides the complexity of the enumerators.  Therefore, using `foreach` is recommended, instead of directly manipulating the enumerator.  
   
  Enumerators can be used to read the data in the collection, but they cannot be used to modify the underlying collection.  
diff --git a/xml/System.Collections/Stack.xml b/xml/System.Collections/Stack.xml
@@ -595,8 +595,7 @@ If <xref:System.Collections.Stack.Count%2A> is less than the capacity of the sta
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [Visual Basic, C#]  
-  
+
  The `foreach` statement of the C# language (`for each` in Visual Basic) hides the complexity of the enumerators.  Therefore, using `foreach` is recommended, instead of directly manipulating the enumerator.  
   
  Enumerators can be used to read the data in the collection, but they cannot be used to modify the underlying collection.  
diff --git a/xml/System.DirectoryServices/PropertyCollection.xml b/xml/System.DirectoryServices/PropertyCollection.xml
@@ -300,8 +300,7 @@
   
  Enumerating through a collection is intrinsically not a thread safe procedure. Even when a collection is synchronized, other threads can still modify the collection, which causes the enumerator to throw an exception. To guarantee thread safety during enumeration, you can either lock the collection during the entire enumeration or catch the exceptions that result from changes made by other threads.  
   
- [Visual Basic, C#]  
-  
+
  The following example shows how to lock the collection using the <xref:System.Collections.ICollection.SyncRoot%2A> during the entire enumeration:  
   
 ```csharp  
@@ -377,8 +376,7 @@ Dim myCollection as New ICollection()
   
  Enumerating through a collection is intrinsically not a thread safe procedure. Even when a collection is synchronized, other threads can still modify the collection, which causes the enumerator to throw an exception. To guarantee thread safety during enumeration, you can either lock the collection during the entire enumeration or catch the exceptions resulting from changes made by other threads.  
   
- [Visual Basic, C#]  
-  
+
  The following code example shows how to lock the collection using the <xref:System.Collections.ICollection.SyncRoot%2A> during the entire enumeration:  
   
 ```csharp  
@@ -810,8 +808,7 @@ Dim myCollection As New ICollection()
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [Visual Basic, C#]  
-  
+
  The `foreach` statement of the C# language (`for each` in Visual Basic) hides the complexity of the enumerators.  Therefore, using `foreach` is recommended instead of directly manipulating the enumerator.  
   
  Enumerators can be used to read the data in the collection, but they cannot be used to modify the underlying collection.  
diff --git a/xml/System.DirectoryServices/SchemaNameCollection.xml b/xml/System.DirectoryServices/SchemaNameCollection.xml
@@ -490,8 +490,7 @@
   
  Enumerating through a collection is intrinsically not a thread-safe procedure. Even when a collection is synchronized, other threads can still modify the collection, which causes the enumerator to throw an exception. To guarantee thread safety during enumeration, you can either lock the collection during the entire enumeration or catch the exceptions resulting from changes made by other threads.  
   
- [Visual Basic, C#]  
-  
+
  The following example shows how to lock the collection using the <xref:System.Collections.ICollection.SyncRoot%2A> during the entire enumeration:  
   
 ```csharp  
@@ -567,8 +566,7 @@ Dim myCollection as New ICollection()
   
  Enumerating through a collection is intrinsically not a thread-safe procedure. Even when a collection is synchronized, other threads can still modify the collection, which causes the enumerator to throw an exception. To guarantee thread safety during enumeration, you can either lock the collection during the entire enumeration or catch the exceptions resulting from changes made by other threads.  
   
- [Visual Basic, C#]  
-  
+
  The following example shows how to lock the collection using the <xref:System.Collections.ICollection.SyncRoot%2A> during the entire enumeration:  
   
 ```csharp  
diff --git a/xml/System.DirectoryServices/SearchResultCollection.xml b/xml/System.DirectoryServices/SearchResultCollection.xml
@@ -467,8 +467,7 @@
   
  Enumerating through a collection is intrinsically not a thread safe procedure. Even when a collection is synchronized, other threads can still modify the collection, which causes the enumerator to throw an exception. To guarantee thread safety during enumeration, you can either lock the collection during the entire enumeration or catch the exceptions resulting from changes made by other threads.  
   
- [Visual Basic, C#]  
-  
+
  The following code example shows how to lock the collection using the <xref:System.Collections.ICollection.SyncRoot%2A> during the entire enumeration:  
   
 ```csharp  
@@ -544,8 +543,7 @@ Dim myCollection as New ICollection()
   
  Enumerating through a collection is intrinsically not a thread safe procedure. Even when a collection is synchronized, other threads can still modify the collection, which causes the enumerator to throw an exception. To guarantee thread safety during enumeration, you can either lock the collection during the entire enumeration or catch the exceptions resulting from changes made by other threads.  
   
- [Visual Basic, C#]  
-  
+
  The following code example shows how to lock the collection using the <xref:System.Collections.ICollection.SyncRoot%2A> during the entire enumeration:  
   
 ```csharp  
diff --git a/xml/System.Management/ManagementObjectCollection.xml b/xml/System.Management/ManagementObjectCollection.xml
@@ -370,8 +370,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [Visual Basic, C#]  
-  
+
  The `foreach` statement of the C# language (`for each` in Visual Basic) hides the complexity of the enumerators.  Therefore, using `foreach` is recommended, instead of directly manipulating the enumerator.  
   
  Enumerators can be used to read the data in the collection, but they cannot be used to modify the underlying collection.  
diff --git a/xml/System.Management/MethodDataCollection.xml b/xml/System.Management/MethodDataCollection.xml
@@ -478,8 +478,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [Visual Basic, C#]  
-  
+
  The `foreach` statement of the C# language (`for each` in Visual Basic) hides the complexity of the enumerators.  Therefore, using `foreach` is recommended, instead of directly manipulating the enumerator.  
   
  Enumerators can be used to read the data in the collection, but they cannot be used to modify the underlying collection.  
diff --git a/xml/System.Management/PropertyDataCollection.xml b/xml/System.Management/PropertyDataCollection.xml
@@ -518,8 +518,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [Visual Basic, C#]  
-  
+
  The `foreach` statement of the C# language (`for each` in Visual Basic) hides the complexity of the enumerators.  Therefore, using `foreach` is recommended, instead of directly manipulating the enumerator.  
   
  Enumerators can be used to read the data in the collection, but they cannot be used to modify the underlying collection.  
diff --git a/xml/System.Management/QualifierDataCollection.xml b/xml/System.Management/QualifierDataCollection.xml
@@ -477,8 +477,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [Visual Basic, C#]  
-  
+
  The `foreach` statement of the C# language (`for each` in Visual Basic) hides the complexity of the enumerators.  Therefore, using `foreach` is recommended, instead of directly manipulating the enumerator.  
   
  Enumerators can be used to read the data in the collection, but they cannot be used to modify the underlying collection.  
diff --git a/xml/System.Reflection.Emit/AssemblyBuilder.xml b/xml/System.Reflection.Emit/AssemblyBuilder.xml
@@ -560,7 +560,6 @@
    
   
 ## Examples  
- [Visual Basic, C#]  
   
  The code example below demonstrates how to create a transient dynamic module using `DefineDynamicModule`.  
   
@@ -646,7 +645,6 @@
    
   
 ## Examples  
- [Visual Basic, C#]  
   
  The code example below demonstrates how to create a transient dynamic module using `DefineDynamicModule`, suppressing symbol information.  
   
@@ -733,7 +731,6 @@
    
   
 ## Examples  
- [Visual Basic, C#]  
   
  The code example below demonstrates how to create a persistent dynamic module using `DefineDynamicModule`.  
   
@@ -827,7 +824,6 @@
    
   
 ## Examples  
- [Visual Basic, C#]  
   
  The code example below demonstrates how to create a persistent dynamic module with symbol emission using `DefineDynamicModule`.  
   
diff --git a/xml/System.Windows.Forms/Control.xml b/xml/System.Windows.Forms/Control.xml
@@ -5302,8 +5302,6 @@ Point clientPoint = targetControl.PointToClient(new Point(de.X, de.Y));
   
  Because the <xref:System.Drawing.Font> is immutable (meaning that you cannot adjust any of its properties), you can only assign the <xref:System.Windows.Forms.Control.Font%2A> property a new <xref:System.Drawing.Font>. However, you can base the new font on the existing font.  
   
- [Visual Basic, C#]  
-  
  The following is an example of how to adjust the existing font to make it bold:  
   
 ```csharp  
diff --git a/xml/System/TypeLoadException.xml b/xml/System/TypeLoadException.xml
@@ -384,8 +384,7 @@
    
   
 ## Examples  
- [Visual Basic, C#]  
-  
+
  The following example generates an exception, and serializes the exception data to a file, and then reconstitutes the exception. For this code example to run, you must provide the fully qualified assembly name. For information about how to obtain the fully qualified assembly name, see [Assembly Names](/dotnet/standard/assembly/names).  
   
  [!code-cpp[TypeLoadException_GetObjectData#1](~/samples/snippets/cpp/VS_Snippets_CLR/TypeLoadException_GetObjectData/CPP/typeloadexception_getobjectdata.cpp#1)]
