review msdn blogs links (#3114)

* review msdn blogs links

* feedback

Author: mairaw

xml/System.Data.SqlClient/SqlColumnEncryptionCertificateStoreProvider.xml

@@ -16,7 +16,7 @@
   <Docs>
     <summary>The implementation of the key store provider for Windows Certificate Store. This class enables using certificates stored in the Windows Certificate Store as column master keys. For details, see <see href="https://docs.microsoft.com/sql/relational-databases/security/encryption/always-encrypted-database-engine">Always Encrypted</see>.</summary>
     <remarks>To be added.</remarks>
-    <related type="ExternalDocumentation" href="https://blogs.msdn.com/b/sqlsecurity/archive/tags/always+encrypted/">Always Encrypted Blog</related>
+    <related type="ExternalDocumentation" href="https://blogs.msdn.microsoft.com/sqlsecurity/tag/always-encrypted/">Always Encrypted (blog posts)</related>
     <related type="ExternalDocumentation" href="https://msdn.microsoft.com/library/mt147923.aspx">Always Encrypted (client development)</related>
   </Docs>
   <Members>

xml/System.Data.SqlClient/SqlColumnEncryptionCngProvider.xml

@@ -23,7 +23,7 @@
   
  ]]></format>
     </remarks>
-    <related type="ExternalDocumentation" href="https://blogs.msdn.com/b/sqlsecurity/archive/tags/always+encrypted/">Getting Started with Always Encrypted</related>
+    <related type="ExternalDocumentation" href="https://blogs.msdn.microsoft.com/sqlsecurity/tag/always-encrypted/">Always Encrypted (blog posts)</related>
     <related type="ExternalDocumentation" href="https://msdn.microsoft.com/library/mt147923.aspx">Always Encrypted (client development)</related>
   </Docs>
   <Members>

xml/System.Data.SqlClient/SqlColumnEncryptionCspProvider.xml

@@ -23,7 +23,7 @@
   
  ]]></format>
     </remarks>
-    <related type="ExternalDocumentation" href="https://blogs.msdn.com/b/sqlsecurity/archive/tags/always+encrypted/">Always Encrypted Blog</related>
+    <related type="ExternalDocumentation" href="https://blogs.msdn.microsoft.com/sqlsecurity/tag/always-encrypted/">Always Encrypted (blog posts)</related>
     <related type="ExternalDocumentation" href="/sql/relational-databases/security/encryption/always-encrypted-client-development">Always Encrypted (client development)</related>
   </Docs>
   <Members>

xml/System.Data.SqlClient/SqlColumnEncryptionKeyStoreProvider.xml

@@ -16,7 +16,7 @@
   <Docs>
     <summary>Base class for all key store providers. A custom provider must derive from this class and override its member functions and then register it using SqlConnection.RegisterColumnEncryptionKeyStoreProviders(). For details see, <see href="https://docs.microsoft.com/sql/relational-databases/security/encryption/always-encrypted-database-engine">Always Encrypted</see>.</summary>
     <remarks>To be added.</remarks>
-    <related type="ExternalDocumentation" href="https://blogs.msdn.com/b/sqlsecurity/archive/tags/always+encrypted/">Always Encrypted Blog</related>
+    <related type="ExternalDocumentation" href="https://blogs.msdn.microsoft.com/sqlsecurity/tag/always-encrypted/">Always Encrypted (blog posts)</related>
     <related type="ExternalDocumentation" href="/sql/relational-databases/security/encryption/always-encrypted-client-development">Always Encrypted (client development)</related>
   </Docs>
   <Members>

xml/System.Data.SqlClient/SqlCommandColumnEncryptionSetting.xml

@@ -26,7 +26,7 @@
   
  ]]></format>
     </remarks>
-    <related type="ExternalDocumentation" href="https://blogs.msdn.com/b/sqlsecurity/archive/2015/06/04/getting-started-with-always-encrypted.aspx">Getting Started with Always Encrypted</related>
+    <related type="ExternalDocumentation" href="https://blogs.msdn.microsoft.com/sqlsecurity/2015/06/04/getting-started-with-always-encrypted/">Getting Started with Always Encrypted (blog post)</related>
     <related type="ExternalDocumentation" href="/sql/relational-databases/security/encryption/always-encrypted-client-development">Always Encrypted (client development)</related>
   </Docs>
   <Members>

xml/System.Data.SqlClient/SqlConnectionColumnEncryptionSetting.xml

@@ -16,7 +16,7 @@
   <Docs>
     <summary>Specifies that Always Encrypted functionality is enabled in a connection. Note that these settings cannot be used to bypass encryption and gain access to plaintext data. For details, see <see href="https://docs.microsoft.com/sql/relational-databases/security/encryption/always-encrypted-database-engine">Always Encrypted (Database Engine)</see>.</summary>
     <remarks>To be added.</remarks>
-    <related type="ExternalDocumentation" href="https://blogs.msdn.com/b/sqlsecurity/archive/2015/06/04/getting-started-with-always-encrypted.aspx">Getting Started with Always Encrypted</related>
+    <related type="ExternalDocumentation" href="https://blogs.msdn.microsoft.com/sqlsecurity/2015/06/04/getting-started-with-always-encrypted/">Getting Started with Always Encrypted (blog post)</related>
     <related type="ExternalDocumentation" href="https://msdn.microsoft.com/library/mt147923.aspx">Always Encrypted (client development)</related>
   </Docs>
   <Members>

xml/System.Security.Cryptography/RSAParameters.xml

@@ -83,7 +83,7 @@
  ]]></format>
     </remarks>
     <related type="Article" href="~/docs/standard/security/cryptographic-services.md">Cryptographic Services</related>
-    <related type="ExternalDocumentation" href="https://blogs.msdn.com/b/shawnfa/archive/2005/11/17/493972.aspx">All About RSAParameters</related>
+    <related type="ExternalDocumentation" href="https://blogs.msdn.microsoft.com/shawnfa/2005/11/17/all-about-rsaparameters/">All About RSAParameters (blog post)</related>
   </Docs>
   <Members>
     <Member MemberName="D">

xml/System.Text/Encoding.xml

@@ -3732,7 +3732,7 @@ In the .NET Framework, the <xref:System.Text.Encoding.GetEncoding%2A> method rel
   
  To calculate the exact array size required by <xref:System.Text.Encoding.GetBytes%2A> to store the resulting bytes, you should use the <xref:System.Text.Encoding.GetByteCount%2A> method. To calculate the maximum array size, use the <xref:System.Text.Encoding.GetMaxByteCount%2A> method. The <xref:System.Text.Encoding.GetByteCount%2A> method generally allows allocation of less memory, while the <xref:System.Text.Encoding.GetMaxByteCount%2A> method generally executes faster.  
   
- <xref:System.Text.Encoding.GetMaxByteCount%2A> retrieves a worst-case number, including the worst case for the currently selected <xref:System.Text.EncoderFallback>. If a fallback is chosen with a potentially large string, <xref:System.Text.Encoding.GetMaxByteCount%2A> retrieves large values, particularly in cases where the worst case for the encoding involves switching modes for every character. For example, this can happen for ISO-2022-JP. For more information, see the blog entry "[What's with Encoding.GetMaxByteCount() and Encoding.GetMaxCharCount()?](https://go.microsoft.com/fwlink/?LinkId=153702)" (http://blogs.msdn.com/shawnste/archive/2005/03/02/383903.aspx).  
+ <xref:System.Text.Encoding.GetMaxByteCount%2A> retrieves a worst-case number, including the worst case for the currently selected <xref:System.Text.EncoderFallback>. If a fallback is chosen with a potentially large string, <xref:System.Text.Encoding.GetMaxByteCount%2A> retrieves large values, particularly in cases where the worst case for the encoding involves switching modes for every character. For example, this can happen for ISO-2022-JP. For more information, see the blog post "[What's with Encoding.GetMaxByteCount() and Encoding.GetMaxCharCount()?](https://blogs.msdn.microsoft.com/shawnste/2005/03/02/whats-with-encoding-getmaxbytecount-and-encoding-getmaxcharcount/).  
   
  In most cases, this method retrieves reasonable values for small strings. For large strings, you might have to choose between using very large buffers and catching errors in the rare case when a more reasonable buffer is too small. You might also want to consider a different approach using <xref:System.Text.Encoding.GetByteCount%2A> or <xref:System.Text.Encoder.Convert%2A?displayProperty=nameWithType>.  
   

xml/System/OutOfMemoryException.xml

@@ -57,7 +57,7 @@ An <xref:System.OutOfMemoryException> exception has two major causes:
   
 -   You are attempting to expand a <xref:System.Text.StringBuilder> object beyond the length defined by its <xref:System.Text.StringBuilder.MaxCapacity%2A?displayProperty=nameWithType> property.  
   
--   The common language runtime cannot allocate enough contiguous memory to successfully perform an operation. This exception can be thrown by any property assignment or method call that requires a memory allocation. For more information on the cause of the <xref:System.OutOfMemoryException> exception, see ["Out of Memory" Does Not Refer to Physical Memory](https://blogs.msdn.com/b/ericlippert/archive/2009/06/08/out-of-memory-does-not-refer-to-physical-memory.aspx).  
+-   The common language runtime cannot allocate enough contiguous memory to successfully perform an operation. This exception can be thrown by any property assignment or method call that requires a memory allocation. For more information on the cause of the <xref:System.OutOfMemoryException> exception, see the blog post ["Out of Memory" Does Not Refer to Physical Memory](https://blogs.msdn.microsoft.com/ericlippert/2009/06/08/out-of-memory-does-not-refer-to-physical-memory/).  
   
      This type of <xref:System.OutOfMemoryException> exception represents a catastrophic failure. If you choose to handle the exception, you should include a `catch` block that calls the <xref:System.Environment.FailFast%2A?displayProperty=nameWithType> method to terminate your app and add an entry to the system event log, as the following example does.  
   

xml/ns-System.Globalization.xml

@@ -5,13 +5,14 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The following MSDN blogs include discussions of the <xref:System.Globalization> namespace and its classes:  
+
+The following blogs include discussions of the <xref:System.Globalization> namespace and its classes:  
   
--   [http://blogs.msdn.com/shawnste/](https://go.microsoft.com/fwlink/?LinkId=160948)  
+- <https://blogs.msdn.microsoft.com/shawnste/>
   
--   [http://blogs.msdn.com/kierans/](https://go.microsoft.com/fwlink/?LinkId=160951)  
+- <https://blogs.msdn.microsoft.com/kierans/>
   
- Note that two of the types in this namespace, <xref:System.Globalization.CultureAndRegionInfoBuilder> and <xref:System.Globalization.CultureAndRegionModifiers>, are found in an assembly named sysglobl.dll. Successfully compiling code that uses these types requires that you add a reference to sysglobl.dll.  
+ Note that two of the .NET Framework types in this namespace, <xref:System.Globalization.CultureAndRegionInfoBuilder> and <xref:System.Globalization.CultureAndRegionModifiers>, are found in an assembly named sysglobl.dll. Successfully compiling code that uses these types requires that you add a reference to sysglobl.dll.  
   
  ]]></format>
     </remarks>