dotnet · mairaw · Mar 29, 2019 · Mar 28, 2019 · Mar 28, 2019 · Mar 28, 2019
diff --git a/xml/System.Diagnostics/EventLog.xml b/xml/System.Diagnostics/EventLog.xml
@@ -1667,7 +1667,7 @@ SVC_UPDATE.EXE
 
  When you create an <xref:System.Diagnostics.EventLog.EntryWritten> delegate, you identify the method that will handle the event. To associate the event with your event handler, add an instance of the delegate to the event. The event handler is called whenever the event occurs, until you remove the delegate. For more information about handling events with delegates, see [Handling and Raising Events](~/docs/standard/events/index.md).  
 
- The system responds to <xref:System.Diagnostics.EventLog.WriteEntry%2A> only if the last write event occurred at least six seconds previously. This implies you will only receive one <xref:System.Diagnostics.EventLog.EntryWritten> event notification within a six-second interval, even if more than one event log change occurs. If you insert a sufficiently long sleep interval (around 10 seconds) between calls to <xref:System.Diagnostics.EventLog.WriteEntry%2A>, you are less likely to miss an event. However, if write events occur more frequently, you might not recieve the event notification until the next interval. Typically, missed event notifications are not lost, but delayed.  
+ The system responds to <xref:System.Diagnostics.EventLog.WriteEntry%2A> only if the last write event occurred at least six seconds previously. This implies you will only receive one <xref:System.Diagnostics.EventLog.EntryWritten> event notification within a six-second interval, even if more than one event log change occurs. If you insert a sufficiently long sleep interval (around 10 seconds) between calls to <xref:System.Diagnostics.EventLog.WriteEntry%2A>, you are less likely to miss an event. However, if write events occur more frequently, you might not receive the event notification until the next interval. Typically, missed event notifications are not lost, but delayed.  
 
 
 

diff --git a/xml/System.IO/Path.xml b/xml/System.IO/Path.xml
@@ -855,7 +855,7 @@ This method obtains the extension of `path` by searching `path` for a period (.)
         <remarks>
           <format type="text/markdown"><![CDATA[  
 
-The returned read-only span contains the characters of the path that follow the last separator in `path`. If the last character in `path` is a volume or directory separator character, the method returns <xref:System.ReadOnlySpan%601.Empty?displayProperty=nameWithtype>. If `path` contains no separator character, the method returns `path`.
+The returned read-only span contains the characters of the path that follow the last separator in `path`. If the last character in `path` is a volume or directory separator character, the method returns <xref:System.ReadOnlySpan%601.Empty?displayProperty=nameWithType>. If `path` contains no separator character, the method returns `path`.
 
          ]]></format>
         </remarks>

diff --git a/xml/System.Management.Instrumentation/WmiConfigurationAttribute.xml b/xml/System.Management.Instrumentation/WmiConfigurationAttribute.xml
@@ -310,7 +310,7 @@
           <format type="text/markdown"><![CDATA[  
 
 ## Remarks  
- A WMI namespace is a category within the WMI repository. The commonly-used root/cimv2 namespace houses classes that describe the Common Information Model, Version 2, defined by the Desktop Management Task Force (DMTF) consortium. You should only expose your providers in that namespace if you expanding upon the standand CIM model. Otherwise, you should create an appropriate namespace that makes clear to users the type of WMI classes they can expect to find in the namespace.  
+ A WMI namespace is a category within the WMI repository. The commonly-used root/cimv2 namespace houses classes that describe the Common Information Model, Version 2, defined by the Desktop Management Task Force (DMTF) consortium. You should only expose your providers in that namespace if you expanding upon the standard CIM model. Otherwise, you should create an appropriate namespace that makes clear to users the type of WMI classes they can expect to find in the namespace.  
 
  ]]></format>
         </remarks>

diff --git a/xml/System.Net.Configuration/HttpListenerTimeoutsElement.xml b/xml/System.Net.Configuration/HttpListenerTimeoutsElement.xml
@@ -19,7 +19,7 @@
       <format type="text/markdown"><![CDATA[  
 
 ## Remarks  
- The timeouts element defines the dafault connection timeout limits for an <xref:System.Net.HttpListener> instance.  
+ The timeouts element defines the default connection timeout limits for an <xref:System.Net.HttpListener> instance.  
 
  ]]></format>
     </remarks>

diff --git a/xml/System.Net.Configuration/SmtpSection.xml b/xml/System.Net.Configuration/SmtpSection.xml
@@ -221,7 +221,7 @@
         <ReturnType>System.Net.Configuration.SmtpSpecifiedPickupDirectoryElement</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the pickup directory that will be used by the SMPT client.</summary>
+        <summary>Gets the pickup directory that will be used by the SMTP client.</summary>
         <value>A <see cref="T:System.Net.Configuration.SmtpSpecifiedPickupDirectoryElement" /> object that specifies the pickup directory folder.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  

diff --git a/xml/System.Net.Http.Headers/CacheControlHeaderValue.xml b/xml/System.Net.Http.Headers/CacheControlHeaderValue.xml
@@ -499,7 +499,7 @@
 ## Remarks  
  This property represents the "no-transform" directive in a cache-control header field on an HTTP request or HTTP response.  
 
- When the <xref:System.Net.Http.Headers.CacheControlHeaderValue.NoTransform%2A> is set to `true`, intermediate caches or rpoxies must not change any aspect of the entity body. Implementors of intermediate caches and proxies have found it useful to convert the media type of certain entity bodies. A non-transparent proxy might, for example, convert between image formats in order to save cache space or to reduce the amount of traffic on a slow link. Serious operational problems occur, however, when these transformations are applied to entity bodies intended for certain kinds of applications.  
+ When the <xref:System.Net.Http.Headers.CacheControlHeaderValue.NoTransform%2A> is set to `true`, intermediate caches or proxies must not change any aspect of the entity body. Implementors of intermediate caches and proxies have found it useful to convert the media type of certain entity bodies. A non-transparent proxy might, for example, convert between image formats in order to save cache space or to reduce the amount of traffic on a slow link. Serious operational problems occur, however, when these transformations are applied to entity bodies intended for certain kinds of applications.  
 
  ]]></format>
         </remarks>

diff --git a/xml/System.Net.PeerToPeer/PeerNameRegistration.xml b/xml/System.Net.PeerToPeer/PeerNameRegistration.xml
@@ -313,7 +313,7 @@
         <summary>Releases all resources used by the <see cref="T:System.Net.PeerToPeer.PeerNameRegistration" /> object.</summary>
         <remarks>To be added.</remarks>
         <block subset="none" type="usage">
-          <para>lways call the Dispose method before destroying the <see cref="T:System.Net.PeerToPeer.PeerNameRegistration" /> object.</para>
+          <para>Always call the Dispose method before destroying the <see cref="T:System.Net.PeerToPeer.PeerNameRegistration" /> object.</para>
         </block>
       </Docs>
     </Member>
@@ -371,7 +371,7 @@
 ## Remarks  
  In the <xref:System.Net> namespace, an <xref:System.Net.IPEndPoint> represents a network endpoint as an IP address and a port number.  For PNRP, an IP address and port value must be provided for each endpoint.  The maximum number of endpoints that can be provided is ten. Automatic address selection is used when this parameter is `null`.  
 
- If a registration method is used that automatically selects the addresses to register, there is no method to determine theaddresses for which the peer name was registered.  That is, the <xref:System.Net.PeerToPeer.PeerNameRegistration.EndPointCollection%2A> property will not be updated to reflect the addresses selected.  
+ If a registration method is used that automatically selects the addresses to register, there is no method to determine the addresses for which the peer name was registered.  That is, the <xref:System.Net.PeerToPeer.PeerNameRegistration.EndPointCollection%2A> property will not be updated to reflect the addresses selected.  
 
  When a peer name is registered for more than one node, each <xref:System.Net.PeerToPeer.PeerNameRegistration> is distinct and the <xref:System.Net.PeerToPeer.PeerNameRegistration.EndPointCollection%2A> property defined on each registration instance will be different. Also, when a <xref:System.Net.PeerToPeer.PeerNameRegistration.PeerName%2A> is registered into more than one <xref:System.Net.PeerToPeer.PeerNameRegistration.Cloud%2A>, each registration is distinct and the collection of endpoints will usually be different for each instance.  
 

diff --git a/xml/System.Net.Security/SslStream.xml b/xml/System.Net.Security/SslStream.xml
@@ -984,7 +984,7 @@
         <param name="serverCertificate">The X509Certificate used to authenticate the server.</param>
         <param name="clientCertificateRequired">A <see cref="T:System.Boolean" /> value that specifies whether the client is asked for a certificate for authentication. Note that this is only a request -- if no certificate is provided, the server still accepts the connection request.</param>
         <param name="checkCertificateRevocation">A <see cref="T:System.Boolean" /> value that specifies whether the certificate revocation list is checked during authentication.</param>
-        <summary>Called by servers to authenticate the server and optionally the client in a client-server connection using the specified certificates and requirements, and using the sytem default security protocol.</summary>
+        <summary>Called by servers to authenticate the server and optionally the client in a client-server connection using the specified certificates and requirements, and using the system default security protocol.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
 

diff --git a/xml/System.Net.Sockets/AddressFamily.xml b/xml/System.Net.Sockets/AddressFamily.xml
@@ -41,9 +41,9 @@
 ## Examples  
  The following example creates a <xref:System.Net.Sockets.Socket> using the InterNetwork <xref:System.Net.Sockets.AddressFamily>.  
 
- [!code-cpp[Socket_Send_Recieve#1](~/samples/snippets/cpp/VS_Snippets_Remoting/Socket_Send_Recieve/CPP/source.cpp#1)]
- [!code-csharp[Socket_Send_Recieve#1](~/samples/snippets/csharp/VS_Snippets_Remoting/Socket_Send_Recieve/CS/source.cs#1)]
- [!code-vb[Socket_Send_Recieve#1](~/samples/snippets/visualbasic/VS_Snippets_Remoting/Socket_Send_Recieve/VB/source.vb#1)]  
+ [!code-cpp[Socket_Send_Receive#1](~/samples/snippets/cpp/VS_Snippets_Remoting/Socket_Send_Receive/CPP/source.cpp#1)]
+ [!code-csharp[Socket_Send_Receive#1](~/samples/snippets/csharp/VS_Snippets_Remoting/Socket_Send_Receive/CS/source.cs#1)]
+ [!code-vb[Socket_Send_Receive#1](~/samples/snippets/visualbasic/VS_Snippets_Remoting/Socket_Send_Receive/VB/source.vb#1)]  
 
  ]]></format>
     </remarks>

diff --git a/xml/System.Net.Sockets/Socket.xml b/xml/System.Net.Sockets/Socket.xml
@@ -249,9 +249,9 @@
 ## Examples  
  The following code example demonstrates how to create an instance of the <xref:System.Net.Sockets.Socket> class.  
 
- [!code-cpp[Socket_Send_Recieve#1](~/samples/snippets/cpp/VS_Snippets_Remoting/Socket_Send_Recieve/CPP/source.cpp#1)]
- [!code-csharp[Socket_Send_Recieve#1](~/samples/snippets/csharp/VS_Snippets_Remoting/Socket_Send_Recieve/CS/source.cs#1)]
- [!code-vb[Socket_Send_Recieve#1](~/samples/snippets/visualbasic/VS_Snippets_Remoting/Socket_Send_Recieve/VB/source.vb#1)]  
+ [!code-cpp[Socket_Send_Receive#1](~/samples/snippets/cpp/VS_Snippets_Remoting/Socket_Send_Receive/CPP/source.cpp#1)]
+ [!code-csharp[Socket_Send_Receive#1](~/samples/snippets/csharp/VS_Snippets_Remoting/Socket_Send_Receive/CS/source.cs#1)]
+ [!code-vb[Socket_Send_Receive#1](~/samples/snippets/visualbasic/VS_Snippets_Remoting/Socket_Send_Receive/VB/source.vb#1)]  
 
  ]]></format>
         </remarks>
@@ -6865,9 +6865,9 @@ The GetHashCode method returns a hash code of this instance. This value can be u
 ## Examples  
  The following receives the data found into `buffer`, and specifies <xref:System.Net.Sockets.SocketFlags.None> for <xref:System.Net.Sockets.SocketFlags>.  
 
- [!code-cpp[Socket_Send_Recieve#4](~/samples/snippets/cpp/VS_Snippets_Remoting/Socket_Send_Recieve/CPP/source.cpp#4)]
- [!code-csharp[Socket_Send_Recieve#4](~/samples/snippets/csharp/VS_Snippets_Remoting/Socket_Send_Recieve/CS/source.cs#4)]
- [!code-vb[Socket_Send_Recieve#4](~/samples/snippets/visualbasic/VS_Snippets_Remoting/Socket_Send_Recieve/VB/source.vb#4)]  
+ [!code-cpp[Socket_Send_Receive#4](~/samples/snippets/cpp/VS_Snippets_Remoting/Socket_Send_Receive/CPP/source.cpp#4)]
+ [!code-csharp[Socket_Send_Receive#4](~/samples/snippets/csharp/VS_Snippets_Remoting/Socket_Send_Receive/CS/source.cs#4)]
+ [!code-vb[Socket_Send_Receive#4](~/samples/snippets/visualbasic/VS_Snippets_Remoting/Socket_Send_Receive/VB/source.vb#4)]  
 
  ]]></format>
         </remarks>

diff --git a/xml/System.Net/Cookie.xml b/xml/System.Net/Cookie.xml
@@ -1025,7 +1025,7 @@
           <format type="text/markdown"><![CDATA[  
 
 ## Remarks  
- The <xref:System.Net.Cookie.Path%2A> property specifies the subset of URIs on the origin server to which this <xref:System.Net.Cookie> applies. If this propery is not specified, then this <xref:System.Net.Cookie> will be sent to all pages on the origin server or servers.  
+ The <xref:System.Net.Cookie.Path%2A> property specifies the subset of URIs on the origin server to which this <xref:System.Net.Cookie> applies. If this property is not specified, then this <xref:System.Net.Cookie> will be sent to all pages on the origin server or servers.  
 
 
 

diff --git a/xml/System.Net/IWebProxyScript.xml b/xml/System.Net/IWebProxyScript.xml
@@ -144,12 +144,12 @@
 ## Remarks  
  When the <xref:System.Net.HttpWebRequest> object is run, it may need to run the WPAD (Web Proxy Automatic Detection) protocol to detect whether a proxy is required for reaching the destination URL. During this process, the system downloads and compiles the PAC (Proxy Auto-Configuration) script in memory and tries to execute the FindProxyForURL function as per the PAC specification.  
 
- When doing so, the system creates an internal application domain inside the application which runs with mimimal permissions and most importantly, it does not grant the UI permission to this new application domain. The evaluation of a proxy and running the FindProxyForURL javascript function happens in the context of this new application domain and during this process the system may need to run several helper functions as per the PAC specification.  
+ When doing so, the system creates an internal application domain inside the application which runs with minimal permissions, and, most importantly, it does not grant the UI permission to this new application domain. The evaluation of a proxy and running the FindProxyForURL javascript function happens in the context of this new application domain and during this process the system may need to run several helper functions as per the PAC specification.  
 
  ]]></format>
         </remarks>
         <forInternalUseOnly />
       </Docs>
     </Member>
   </Members>
-</Type>
+</Type>
diff --git a/xml/System.Printing.IndexedProperties/PrintDateTimeProperty.xml b/xml/System.Printing.IndexedProperties/PrintDateTimeProperty.xml
@@ -154,7 +154,7 @@
       <Docs>
         <param name="attribRef">The object that is converted.</param>
         <summary>Provides implicit conversion from a pointer to a <see cref="T:System.Printing.IndexedProperties.PrintDateTimeProperty" /> to a <see cref="T:System.DateTime" />.</summary>
-        <returns>The converted PrintDateTimePropety object to a DateTime object.</returns>
+        <returns>The <see cref="T:System.Printing.IndexedProperties.PrintDateTimeProperty" /> object converted to a <see cref="System.DateTime" /> object.</returns>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -181,4 +181,4 @@
       </Docs>
     </Member>
   </Members>
-</Type>
+</Type>
Original file line number	Diff line number	Diff line change
Expand Up		@@ -1667,7 +1667,7 @@ SVC_UPDATE.EXE

		When you create an <xref:System.Diagnostics.EventLog.EntryWritten> delegate, you identify the method that will handle the event. To associate the event with your event handler, add an instance of the delegate to the event. The event handler is called whenever the event occurs, until you remove the delegate. For more information about handling events with delegates, see [Handling and Raising Events](~/docs/standard/events/index.md).

		The system responds to <xref:System.Diagnostics.EventLog.WriteEntry%2A> only if the last write event occurred at least six seconds previously. This implies you will only receive one <xref:System.Diagnostics.EventLog.EntryWritten> event notification within a six-second interval, even if more than one event log change occurs. If you insert a sufficiently long sleep interval (around 10 seconds) between calls to <xref:System.Diagnostics.EventLog.WriteEntry%2A>, you are less likely to miss an event. However, if write events occur more frequently, you might not recieve the event notification until the next interval. Typically, missed event notifications are not lost, but delayed.
		The system responds to <xref:System.Diagnostics.EventLog.WriteEntry%2A> only if the last write event occurred at least six seconds previously. This implies you will only receive one <xref:System.Diagnostics.EventLog.EntryWritten> event notification within a six-second interval, even if more than one event log change occurs. If you insert a sufficiently long sleep interval (around 10 seconds) between calls to <xref:System.Diagnostics.EventLog.WriteEntry%2A>, you are less likely to miss an event. However, if write events occur more frequently, you might not receive the event notification until the next interval. Typically, missed event notifications are not lost, but delayed.



Expand Down