dotnet · mairaw · Jan 6, 2020 · Jan 6, 2020
diff --git a/docs/standard/assembly/file-format.md b/docs/standard/assembly/file-format.md
@@ -2,7 +2,6 @@
 title: .NET assembly file format
 description: Learn about the .NET assembly file format, which is used to describe and contain .NET apps and libraries.
 author: richlander
-ms.author: mairaw
 ms.date: 08/20/2019
 ms.technology: dotnet-standard
 ms.assetid: 6520323e-ff28-4c8a-ba80-e64a413199e6

diff --git a/docs/standard/assembly/strong-named.md b/docs/standard/assembly/strong-named.md
@@ -5,8 +5,6 @@ helpviewer_keywords:
   - "strong-named assemblies, about strong-named assemblies"
   - "assemblies [.NET Framework], strong-named"
 ms.assetid: d4a80263-f3e0-4d81-9b61-f0cbeae3797b
-author: "mairaw"
-ms.author: "mairaw"
 ---
 # Strong-named assemblies
 

diff --git a/docs/standard/collections/commonly-used-collection-types.md b/docs/standard/collections/commonly-used-collection-types.md
@@ -12,8 +12,6 @@ helpviewer_keywords:
   - "Collections classes"
   - "generic collections"
 ms.assetid: f5d4c6a4-0d7b-4944-a9fb-3b12d9ebfd55
-author: "mairaw"
-ms.author: "mairaw"
 ---
 # Commonly Used Collection Types
 Collection types are the common variations of data collections, such as hash tables, queues, stacks, bags, dictionaries, and lists.  

diff --git a/docs/standard/collections/comparisons-and-sorts-within-collections.md b/docs/standard/collections/comparisons-and-sorts-within-collections.md
@@ -12,8 +12,6 @@ helpviewer_keywords:
   - "Equals method"
   - "collections [.NET Framework], comparisons"
 ms.assetid: 5e4d3b45-97f0-423c-a65f-c492ed40e73b
-author: "mairaw"
-ms.author: "mairaw"
 ---
 # Comparisons and Sorts Within Collections
 The <xref:System.Collections> classes perform comparisons in almost all the processes involved in managing collections, whether searching for the element to remove or returning the value of a key-and-value pair.  

diff --git a/docs/standard/collections/hashtable-and-dictionary-collection-types.md b/docs/standard/collections/hashtable-and-dictionary-collection-types.md
@@ -10,8 +10,6 @@ helpviewer_keywords:
   - "hash function"
   - "collections [.NET Framework], Hashtable collection type"
 ms.assetid: bfc20837-3d02-4fc7-8a8f-c5215b6b7913
-author: "mairaw"
-ms.author: "mairaw"
 ---
 # Hashtable and Dictionary Collection Types
 The <xref:System.Collections.Hashtable?displayProperty=nameWithType> class, and the <xref:System.Collections.Generic.Dictionary%602?displayProperty=nameWithType> and <xref:System.Collections.Concurrent.ConcurrentDictionary%602?displayProperty=nameWithType> generic classes, implement the <xref:System.Collections.IDictionary?displayProperty=nameWithType> interface. The <xref:System.Collections.Generic.Dictionary%602> generic class also implements the <xref:System.Collections.Generic.IDictionary%602> generic interface. Therefore, each element in these collections is a key-and-value pair.  

diff --git a/docs/standard/collections/index.md b/docs/standard/collections/index.md
@@ -10,8 +10,6 @@ helpviewer_keywords:
   - "Collections classes"
   - "collections [.NET Framework]"
 ms.assetid: 60cc581f-1db5-445b-ba04-a173396bf872
-author: "mairaw"
-ms.author: "mairaw"
 ---
 # Collections and Data Structures
 Similar data can often be handled more efficiently when stored and manipulated as a collection. You can use the <xref:System.Array?displayProperty=nameWithType> class or the classes in the <xref:System.Collections>, <xref:System.Collections.Generic>, <xref:System.Collections.Concurrent>, System.Collections.Immutable namespaces to add, remove, and modify either individual elements or a range of elements in a collection.  

diff --git a/docs/standard/collections/selecting-a-collection-class.md b/docs/standard/collections/selecting-a-collection-class.md
@@ -10,8 +10,6 @@ helpviewer_keywords:
   - "Collections classes"
   - "grouping data in collections, selecting collection class"
 ms.assetid: ba049f9a-ce87-4cc4-b319-3f75c8ddac8a
-author: "mairaw"
-ms.author: "mairaw"
 ---
 # Selecting a Collection Class
 

diff --git a/docs/standard/collections/sorted-collection-types.md b/docs/standard/collections/sorted-collection-types.md
@@ -9,8 +9,6 @@ helpviewer_keywords:
   - "SortedList collection type"
   - "collections [.NET Framework], SortedList collection type"
 ms.assetid: 3db965b2-36a6-4b12-b76e-7f074ff7275a
-author: "mairaw"
-ms.author: "mairaw"
 ---
 # Sorted Collection Types
 The <xref:System.Collections.SortedList?displayProperty=nameWithType> class, the <xref:System.Collections.Generic.SortedList%602?displayProperty=nameWithType> generic class, and the <xref:System.Collections.Generic.SortedDictionary%602?displayProperty=nameWithType> generic class are similar to the <xref:System.Collections.Hashtable> class and the <xref:System.Collections.Generic.Dictionary%602> generic class in that they implement the <xref:System.Collections.IDictionary> interface, but they maintain their elements in sort order by key, and they do not have the O(1) insertion and retrieval characteristic of hash tables. The three classes have several features in common:  

diff --git a/docs/standard/collections/thread-safe/blockingcollection-overview.md b/docs/standard/collections/thread-safe/blockingcollection-overview.md
@@ -8,8 +8,6 @@ dev_langs:
 helpviewer_keywords: 
   - "BlockingCollection, overview"
 ms.assetid: 987ea3d7-0ad5-4238-8b64-331ce4eb3f0b
-author: "mairaw"
-ms.author: "mairaw"
 ---
 # BlockingCollection Overview
 <xref:System.Collections.Concurrent.BlockingCollection%601> is a thread-safe collection class that provides the following features:  

diff --git a/docs/standard/collections/thread-safe/how-to-add-and-remove-items.md b/docs/standard/collections/thread-safe/how-to-add-and-remove-items.md
@@ -8,8 +8,6 @@ dev_langs:
 helpviewer_keywords: 
   - "thread-safe collections, concurrent dictionary"
 ms.assetid: 81b64b95-13f7-4532-9249-ab532f629598
-author: "mairaw"
-ms.author: "mairaw"
 ---
 # How to: Add and Remove Items from a ConcurrentDictionary
 This example shows how to add, retrieve, update, and remove items from a <xref:System.Collections.Concurrent.ConcurrentDictionary%602?displayProperty=nameWithType>. This collection class is a thread-safe implementation. We recommend that you use it whenever multiple threads might be attempting to access the elements concurrently.  

diff --git a/docs/standard/collections/thread-safe/how-to-add-and-take-items.md b/docs/standard/collections/thread-safe/how-to-add-and-take-items.md
@@ -8,8 +8,6 @@ dev_langs:
 helpviewer_keywords: 
   - "thread-safe collections, blocking dictionary"
 ms.assetid: 38f2f3d8-15e5-4bf4-9c83-2b5b6f22bad1
-author: "mairaw"
-ms.author: "mairaw"
 ---
 # How to: Add and Take Items Individually from a BlockingCollection
 This example shows how to add and remove items from a <xref:System.Collections.Concurrent.BlockingCollection%601> in both a blocking and a non-blocking manner. For more information on <xref:System.Collections.Concurrent.BlockingCollection%601>, see [BlockingCollection Overview](../../../../docs/standard/collections/thread-safe/blockingcollection-overview.md).  

diff --git a/docs/standard/collections/thread-safe/how-to-add-bounding-and-blocking.md b/docs/standard/collections/thread-safe/how-to-add-bounding-and-blocking.md
@@ -5,8 +5,6 @@ ms.technology: dotnet-standard
 helpviewer_keywords: 
   - "thread-safe collections, custom blocking collections"
 ms.assetid: 4c2492de-3876-4873-b5a1-000bb404d770
-author: "mairaw"
-ms.author: "mairaw"
 ---
 # How to: Add Bounding and Blocking Functionality to a Collection
 This example shows how to add bounding and blocking functionality to a custom collection class by implementing the <xref:System.Collections.Concurrent.IProducerConsumerCollection%601?displayProperty=nameWithType> interface in the class, and then using a class instance as the internal storage mechanism for a <xref:System.Collections.Concurrent.BlockingCollection%601?displayProperty=nameWithType>. For more information about bounding and blocking, see [BlockingCollection Overview](../../../../docs/standard/collections/thread-safe/blockingcollection-overview.md).  

diff --git a/docs/standard/collections/thread-safe/how-to-create-an-object-pool.md b/docs/standard/collections/thread-safe/how-to-create-an-object-pool.md
@@ -8,8 +8,6 @@ dev_langs:
 helpviewer_keywords: 
   - "object pool, in .NET Framework"
 ms.assetid: 0480e7ff-b6f9-480e-a889-2ed4264d8372
-author: "mairaw"
-ms.author: "mairaw"
 ---
 # How to: Create an Object Pool by Using a ConcurrentBag
 This example shows how to use a concurrent bag to implement an object pool. Object pools can improve application performance in situations where you require multiple instances of a class and the class is expensive to create or destroy. When a client program requests a new object, the object pool first attempts to provide one that has already been created and returned to the pool. If none is available, only then is a new object created.  

diff --git a/docs/standard/collections/thread-safe/how-to-use-arrays-of-blockingcollections.md b/docs/standard/collections/thread-safe/how-to-use-arrays-of-blockingcollections.md
@@ -8,8 +8,6 @@ dev_langs:
 helpviewer_keywords: 
   - "thread-safe collections, blocking collections in pipeline"
 ms.assetid: a39c7ec3-3ad7-4f4d-8fe4-b3e9dbabe2ed
-author: "mairaw"
-ms.author: "mairaw"
 ---
 # How to: Use Arrays of Blocking Collections in a Pipeline
 The following example shows how to use arrays of <xref:System.Collections.Concurrent.BlockingCollection%601?displayProperty=nameWithType> objects with static methods such as <xref:System.Collections.Concurrent.BlockingCollection%601.TryAddToAny%2A> and <xref:System.Collections.Concurrent.BlockingCollection%601.TryTakeFromAny%2A> to implement fast and flexible data transfer between components.  

diff --git a/docs/standard/collections/thread-safe/how-to-use-foreach-to-remove.md b/docs/standard/collections/thread-safe/how-to-use-foreach-to-remove.md
@@ -8,8 +8,6 @@ dev_langs:
 helpviewer_keywords:
   - "thread-safe collections, how to enumerate blocking collection"
 ms.assetid: 2096103c-22f7-420d-b631-f102bc33a6dd
-author: "mairaw"
-ms.author: "mairaw"
 ---
 
 # How to: Use ForEach to Remove Items in a BlockingCollection

diff --git a/docs/standard/collections/thread-safe/index.md b/docs/standard/collections/thread-safe/index.md
@@ -5,8 +5,6 @@ ms.technology: dotnet-standard
 helpviewer_keywords: 
   - "thread-safe collections, overview"
 ms.assetid: 2e7ca21f-786c-4367-96be-0cf3f3dcc6bd
-author: "mairaw"
-ms.author: "mairaw"
 ---
 # Thread-Safe Collections
 The .NET Framework 4 introduces the <xref:System.Collections.Concurrent?displayProperty=nameWithType> namespace, which includes several collection classes that are both thread-safe and scalable. Multiple threads can safely and efficiently add or remove items from these collections, without requiring additional synchronization in user code. When you write new code, use the concurrent collection classes whenever multiple threads will write to the collection concurrently. If you are only reading from a shared collection, then you can use the classes in the <xref:System.Collections.Generic?displayProperty=nameWithType> namespace. We recommend that you do not use 1.0 collection classes unless you are required to target the .NET Framework 1.1 or earlier runtime.  

diff --git a/docs/standard/collections/thread-safe/when-to-use-a-thread-safe-collection.md b/docs/standard/collections/thread-safe/when-to-use-a-thread-safe-collection.md
@@ -5,8 +5,6 @@ ms.technology: dotnet-standard
 helpviewer_keywords: 
   - "thread-safe collections, when to upgrade"
 ms.assetid: a9babe97-e457-4ff3-b528-a1bc940d5320
-author: "mairaw"
-ms.author: "mairaw"
 ---
 # When to Use a Thread-Safe Collection
 The .NET Framework 4 introduces five new collection types that are specially designed to support multi-threaded add and remove operations. To achieve thread-safety, these new types use various kinds of efficient locking and lock-free synchronization mechanisms. Synchronization adds overhead to an operation. The amount of overhead depends on the kind of synchronization that is used, the kind of operations that are performed, and other factors such as the number of threads that are trying to concurrently access the collection.  

diff --git a/docs/standard/collections/when-to-use-generic-collections.md b/docs/standard/collections/when-to-use-generic-collections.md
@@ -6,8 +6,6 @@ helpviewer_keywords:
   - "collections [.NET Framework], generic"
   - "generic collections [.NET Framework]"
 ms.assetid: e7b868b1-11fe-4ac5-bed3-de68aca47739
-author: "mairaw"
-ms.author: "mairaw"
 ---
 # When to Use Generic Collections
 Using generic collections is generally recommended, because you gain the immediate benefit of type safety without having to derive from a base collection type and implement type-specific members. Generic collection types also generally perform better than the corresponding nongeneric collection types (and better than types that are derived from nongeneric base collection types) when the collection elements are value types, because with generics there is no need to box the elements.  

diff --git a/docs/standard/data/xml/accessing-attributes-in-the-dom.md b/docs/standard/data/xml/accessing-attributes-in-the-dom.md
@@ -6,8 +6,6 @@ dev_langs:
   - "csharp"
   - "vb"
 ms.assetid: ce2df341-a1a4-4e97-8e1b-cd45b8e3e71e
-author: "mairaw"
-ms.author: "mairaw"
 ---
 
 # Accessing Attributes in the DOM

diff --git a/docs/standard/data/xml/accessing-strongly-typed-xml-data-using-xpathnavigator.md b/docs/standard/data/xml/accessing-strongly-typed-xml-data-using-xpathnavigator.md
@@ -6,8 +6,6 @@ dev_langs:
   - "csharp"
   - "vb"
 ms.assetid: 898e0f52-8a7c-4d1f-afcd-6ffb28b050b4
-author: "mairaw"
-ms.author: "mairaw"
 ---
 # Accessing Strongly Typed XML Data Using XPathNavigator
 As an instance of the XPath 2.0 data model, the <xref:System.Xml.XPath.XPathNavigator> class can contain strongly-typed data that maps to common language runtime (CLR) types. According to the XPath 2.0 data model, only elements and attributes can contain strongly-typed data. The <xref:System.Xml.XPath.XPathNavigator> class provides mechanisms for accessing data within an <xref:System.Xml.XPath.XPathDocument> or <xref:System.Xml.XmlDocument> object as strongly-typed data as well as mechanisms for converting from one data type to another.  

diff --git a/docs/standard/data/xml/accessing-xml-data-using-xpathnavigator.md b/docs/standard/data/xml/accessing-xml-data-using-xpathnavigator.md
@@ -3,8 +3,6 @@ title: "Accessing XML Data using XPathNavigator"
 ms.date: "03/30/2017"
 ms.technology: dotnet-standard
 ms.assetid: c57b46e6-5c77-408f-bc4e-67a5dcc9cc05
-author: "mairaw"
-ms.author: "mairaw"
 ---
 # Accessing XML Data using XPathNavigator
 The <xref:System.Xml.XPath.XPathNavigator> class provides methods to navigate nodes, extract XML data and access strongly typed XML data in an <xref:System.Xml.XPath.XPathDocument> or <xref:System.Xml.XmlDocument> object.  

diff --git a/...andard/data/xml/attribute-and-namespace-node-navigation-using-xpathnavigator.md b/...andard/data/xml/attribute-and-namespace-node-navigation-using-xpathnavigator.md
@@ -3,8 +3,6 @@ title: "Attribute and Namespace Node Navigation Using XPathNavigator"
 ms.date: "03/30/2017"
 ms.technology: dotnet-standard
 ms.assetid: 23975f88-e0af-4b88-93de-9e20e11880ad
-author: "mairaw"
-ms.author: "mairaw"
 ---
 # Attribute and Namespace Node Navigation Using XPathNavigator
 The <xref:System.Xml.XPath.XPathNavigator> class provides two sets of navigation methods, the first set, found in the [Node Set Navigation Using XPathNavigator](../../../../docs/standard/data/xml/node-set-navigation-using-xpathnavigator.md) topic, are used to navigate *node sets* in an <xref:System.Xml.XPath.XPathDocument> or <xref:System.Xml.XmlDocument> object. The second set, described in this topic, are used to navigate *attribute and namespace nodes* in an <xref:System.Xml.XPath.XPathDocument> or <xref:System.Xml.XmlDocument> object.  

diff --git a/docs/standard/data/xml/building-xml-schemas.md b/docs/standard/data/xml/building-xml-schemas.md
@@ -7,8 +7,6 @@ dev_langs:
   - "vb"
   - "cpp"
 ms.assetid: 8a5ea56c-0140-4b51-8997-875ae6a8e0cb
-author: "mairaw"
-ms.author: "mairaw"
 ---
 # Building XML Schemas
 The classes in the <xref:System.Xml.Schema?displayProperty=nameWithType> namespace map to the structures defined in the World Wide Web Consortium (W3C) XML Schema Recommendation and can be used to build XML schemas in-memory.  

diff --git a/docs/standard/data/xml/changing-namespace-declarations-in-an-xml-document.md b/docs/standard/data/xml/changing-namespace-declarations-in-an-xml-document.md
@@ -6,8 +6,6 @@ dev_langs:
   - "csharp"
   - "vb"
 ms.assetid: a2758f40-e497-4964-8d8d-1bb68af14dcd
-author: "mairaw"
-ms.author: "mairaw"
 ---
 # Changing Namespace Declarations in an XML Document
 The **XmlDocument** exposes namespace declarations and **xmlns** attributes as part of the document object model. These are stored in the **XmlDocument**, so when you save the document, it can preserve the location of those attributes. Changing these attributes has no affect on the **Name**, **NamespaceURI**, and **Prefix** properties of other nodes already in the tree. For example, if you load the following document, then the `test` element has **NamespaceURI** `123.`  

diff --git a/docs/standard/data/xml/changing-namespace-prefix-properties.md b/docs/standard/data/xml/changing-namespace-prefix-properties.md
@@ -6,8 +6,6 @@ dev_langs:
   - "csharp"
   - "vb"
 ms.assetid: d5c87cbe-4d69-429f-aad5-3103c2ca2770
-author: "mairaw"
-ms.author: "mairaw"
 ---
 # Changing Namespace Prefix Properties
 The **XmlNode** class allows you to change the namespace prefix associated with a given node. For example, the following code shows the prefix of an element being changed.  

diff --git a/docs/standard/data/xml/compiled-xpath-expressions.md b/docs/standard/data/xml/compiled-xpath-expressions.md
@@ -6,8 +6,6 @@ dev_langs:
   - "csharp"
   - "vb"
 ms.assetid: e25dd95f-b64c-4d8b-a3a4-379e1aa0ad55
-author: "mairaw"
-ms.author: "mairaw"
 ---
 # Compiled XPath Expressions
 An <xref:System.Xml.XPath.XPathExpression> object represents a compiled XPath query returned from either the static <xref:System.Xml.XPath.XPathExpression.Compile%2A> method of the <xref:System.Xml.XPath.XPathExpression> class or the <xref:System.Xml.XPath.XPathNavigator.Compile%2A> method of the <xref:System.Xml.XPath.XPathNavigator> class.  

diff --git a/docs/standard/data/xml/conversion-of-xml-data-types.md b/docs/standard/data/xml/conversion-of-xml-data-types.md
@@ -6,8 +6,6 @@ dev_langs:
   - "csharp"
   - "vb"
 ms.assetid: a2aa99ba-8239-4818-9281-f1d72ee40bde
-author: "mairaw"
-ms.author: "mairaw"
 ---
 # Conversion of XML Data Types
 The majority of the methods found in an **XmlConvert** class are used to convert data between strings and strongly-typed formats. Methods are locale independent. This means that they do not take into account any locale settings when doing conversion.  

diff --git a/docs/standard/data/xml/converting-dotnet-types-to-strings.md b/docs/standard/data/xml/converting-dotnet-types-to-strings.md
@@ -3,8 +3,6 @@ title: "Converting .NET Framework Types to Strings"
 ms.date: "03/30/2017"
 ms.technology: dotnet-standard
 ms.assetid: dc2e2b65-f623-4dc3-938b-d2a054d6832c
-author: "mairaw"
-ms.author: "mairaw"
 ---
 # Converting .NET Framework Types to Strings
 If you want to convert a .NET Framework type to a string, use the **ToString** method. The **ToString** method returns a string representation of the type passed in. The following table lists the .NET Framework types that return a string in a format that maps to the XML Schema (XSD) specifications.  

diff --git a/docs/standard/data/xml/converting-strings-to-dotnet-data-types.md b/docs/standard/data/xml/converting-strings-to-dotnet-data-types.md
@@ -6,8 +6,6 @@ dev_langs:
   - "csharp"
   - "vb"
 ms.assetid: 65455ef3-9120-412c-819b-d0f59f88ac09
-author: "mairaw"
-ms.author: "mairaw"
 ---
 # Converting Strings to .NET Framework Data Types
 If you want to convert a string to a .NET Framework data type, use the **XmlConvert** method that fits the application requirements. For a list of all conversion methods available in the **XmlConvert** class, see <xref:System.Xml.XmlConvert>.  

diff --git a/docs/standard/data/xml/copy-existing-nodes.md b/docs/standard/data/xml/copy-existing-nodes.md
@@ -3,8 +3,6 @@ title: "Copy Existing Nodes"
 ms.date: "03/30/2017"
 ms.technology: dotnet-standard
 ms.assetid: 2aa8f65c-cc62-4638-9c46-129dc15be786
-author: "mairaw"
-ms.author: "mairaw"
 ---
 # Copy Existing Nodes
 There are many methods and properties in the XML Document Object Model (DOM)you can use to select a node, such as **SelectSingleNode**, **ChildNodes[int i]**, **Attributes[int i]**. Once the node is selected, you can insert it into the tree using one of the insert methods that work for that particular node type. The only restriction to inserting a node into the tree is that the document must still be well-formed after the node is inserted. When an existing node is inserted into the DOM tree, it is removed from its original position and added to its target position.  

diff --git a/docs/standard/data/xml/copying-document-fragments.md b/docs/standard/data/xml/copying-document-fragments.md
@@ -3,8 +3,6 @@ title: "Copying Document Fragments"
 ms.date: "03/30/2017"
 ms.technology: dotnet-standard
 ms.assetid: cf424bbe-81b7-40d2-9978-9b727da94d80
-author: "mairaw"
-ms.author: "mairaw"
 ---
 # Copying Document Fragments
 You can create an **XmlDocumentFragment** node and then add nodes under it. When the **XmlDocumentFragment** is inserted with the **InsertNode** method, the **XmlDocumentFragment** node is not copied, but its child nodes are inserted in the XML Document Object Model (DOM).  

diff --git a/docs/standard/data/xml/copying-existing-nodes-from-one-document-to-another.md b/docs/standard/data/xml/copying-existing-nodes-from-one-document-to-another.md
@@ -3,8 +3,6 @@ title: "Copying Existing Nodes from One Document to Another"
 ms.date: "03/30/2017"
 ms.technology: dotnet-standard
 ms.assetid: 3caa78c1-3448-4b7b-b83c-228ee857635e
-author: "mairaw"
-ms.author: "mairaw"
 ---
 # Copying Existing Nodes from One Document to Another
 The **ImportNode** method is the mechanism by which a node or entire node subtree is copied from one **XmlDocument** to another. The node returned from the call is a copy of the node from the source document, including attribute values, the node name, node type, and all namespace-related attributes such as the prefix, local name, and namespace Uniform Resource Identifier (URI). The source document is not changed. After you have imported the node, you still have to add it to the tree using one of the methods used to insert nodes.  

diff --git a/docs/standard/data/xml/create-new-nodes-in-the-dom.md b/docs/standard/data/xml/create-new-nodes-in-the-dom.md
@@ -3,8 +3,6 @@ title: "Create New Nodes in the DOM"
 ms.date: "03/30/2017"
 ms.technology: dotnet-standard
 ms.assetid: 6c2b9789-b61a-49f9-b33f-db01a945edf2
-author: "mairaw"
-ms.author: "mairaw"
 ---
 # Create New Nodes in the DOM
 The <xref:System.Xml.XmlDocument> has a create method for all of the node types. Supply the method with a name when required, and content or other parameters for those nodes that have content (for example, a text node), and the node is created. The following methods are ones that need a name and a few other parameters filled to create an appropriate node.  

diff --git a/docs/standard/data/xml/creating-new-attributes-for-elements-in-the-dom.md b/docs/standard/data/xml/creating-new-attributes-for-elements-in-the-dom.md
@@ -6,8 +6,6 @@ dev_langs:
   - "csharp"
   - "vb"
 ms.assetid: dd6dc920-b011-418a-b3db-f1580a7d9251
-author: "mairaw"
-ms.author: "mairaw"
 ---
 # Creating New Attributes for Elements in the DOM
 

diff --git a/docs/standard/data/xml/creating-new-entity-references.md b/docs/standard/data/xml/creating-new-entity-references.md
@@ -3,8 +3,6 @@ title: "Creating New Entity References"
 ms.date: "03/30/2017"
 ms.technology: dotnet-standard
 ms.assetid: a42f81b3-0403-4e34-b346-7d2129804e54
-author: "mairaw"
-ms.author: "mairaw"
 ---
 # Creating New Entity References
 The **CreateEntityReference** method creates a new **XmlEntityReference** node. The XML Document Object Model (DOM) looks to see if the entity name being referenced has already been declared. If it has, the child nodes of **XmlEntityReference** node are copied from the entity declaration node. If there is no entity declaration that matches, an empty text node is attached as the only child of the entity reference node. Because the child nodes of the **XmlEntityReference** node are copies of other nodes, these child nodes are read-only and cannot be modified.