Fixed typos in two files and removed "en-us" from a link in a third file.

Author: DennisLee-DennisLee

docs/profiling/analyze-energy-use-in-store-apps.md

@@ -141,7 +141,7 @@ if (performance && performance.mark) {
 
 ## Other resources  
 
--   The **Connection state and cost management** sections for [C#/VB/C++ and XAML](/previous-versions/windows/apps/hh452985\(v\=win.10\)) and [JavaScript and HTML](https://msdn.microsoft.com/en-us/372afa6a-1c7c-4657-967d-03a77cd8e933) in the Windows Dev Center describe the Windows APIs that provide network connectivity information that your app can use to minimize the cost of network traffic.  
+-   The **Connection state and cost management** sections for [C#/VB/C++ and XAML](/previous-versions/windows/apps/hh452985\(v\=win.10\)) and [JavaScript and HTML](https://msdn.microsoft.com/372afa6a-1c7c-4657-967d-03a77cd8e933) in the Windows Dev Center describe the Windows APIs that provide network connectivity information that your app can use to minimize the cost of network traffic.  
 
      The Visual Studio simulator for UWP apps enables you to simulate data connection properties of the network information APIs. See [Run UWP apps in the simulator](../debugger/run-windows-store-apps-in-the-simulator.md)  
 

docs/profiling/beginners-guide-to-performance-profiling.md

@@ -63,7 +63,7 @@ In this tutorial, you will:
 
      ![Diagnostics Tools Summary Tab](../profiling/media/DiagToolsSummaryTab.png "DiagToolsSummaryTab")
 
-     For more information on the events, see [Searching and filtering the Events tab of the Diagnostic Tools window](https://blogs.msdn.microsoft.com/devops/2015/11/12/searching-and-filtering-the-events-tab-of-the-diagnostic-tools-window/)
+     For more information on the events, see [Searching and filtering the Events tab of the Diagnostic Tools window](https://blogs.msdn.microsoft.com/devops/2015/11/12/searching-and-filtering-the-events-tab-of-the-diagnostic-tools-window/).
 
 6.  Run the scenario that will cause your first breakpoint to be hit.
 

docs/profiling/performance-rules-by-id.md

@@ -28,8 +28,8 @@ ms.workload:
 | [DA0011: Expensive CompareTo](../profiling/da0011-expensive-compareto.md) | The CompareTo method of the type is expensive or allocates memory. |
 | [DA0012: Significant amount of Reflection](../profiling/da0012-significant-amount-of-reflection.md) | Calls to the System.Reflection methods such as InvokeMember and GetMember or to Type methods such as MemberInvoke are a significant proportion of the profiling data. When you can, consider replacing these methods with early binding to the methods of dependent assemblies. |
 | [DA0013: High usage of String.Split or String.Substring](../profiling/da0013-high-usage-of-string-split-or-string-substring.md) | Calls to the System.String.Split or System.String.Substring methods are a signifiicant portion of the profiling data. Consider using System.String.IndexOf or System.String.IndexOfAny if you're testing for the existence of a substring in a string. |
-| [DA0014: Extremely high rates of paging active memory to disk](../profiling/da0014-extremely-high-rates-of-paging-active-memory-to-disk.md) | System performance data that was collected in the profiling run indicates an enormous rate of paging active memory to and from the disk occurred throughout the profiling run. Paging rates at this level usually will impact application performance and responsiveness. Consider reducing memory allocations by revising algorithms. You might also have to consider the memory requirements of your application. running profiling again on a computer that has more memory. |
-| [DA0017: High rates of paging active memory to disk](../profiling/da0017-high-rates-of-paging-active-memory-to-disk.md) | System performance data that was collected in the profiling run indicates a high rate of paging active memory to and from the disk occurred throughout the profiling run. Paging rates at this level usually will impact application performance and responsiveness. Consider reducing memory allocations by revising algorithms. You might also have to consider the memory requirements of your application. running profiling again on a computer that has more memory. |
+| [DA0014: Extremely high rates of paging active memory to disk](../profiling/da0014-extremely-high-rates-of-paging-active-memory-to-disk.md) | System performance data that was collected in the profiling run indicates an enormous rate of paging active memory to and from the disk occurred throughout the profiling run. Paging rates at this level usually will impact application performance and responsiveness. Consider reducing memory allocations by revising algorithms. You might also have to consider the memory requirements of your application, or running profiling again on a computer that has more memory. |
+| [DA0017: High rates of paging active memory to disk](../profiling/da0017-high-rates-of-paging-active-memory-to-disk.md) | System performance data that was collected in the profiling run indicates a high rate of paging active memory to and from the disk occurred throughout the profiling run. Paging rates at this level usually will impact application performance and responsiveness. Consider reducing memory allocations by revising algorithms. You might also have to consider the memory requirements of your application, or running profiling again on a computer that has more memory. |
 | [DA0018: 32-bit Application running at process managed memory limits](../profiling/da0018-32-bit-application-running-at-process-managed-memory-limits.md) | System data that was collected during the profiling run indicates the .NET Framework memory heaps approached the highest size the managed heaps can grow to in a 32-bit process. The value reported is the highest observed value of the heaps while the profiled process being was active. Consider optimizing the use of managed resources by the application. |
 | [DA0021: High rate of Gen 1 garbage collections](../profiling/da0021-high-rate-of-gen-1-garbage-collections.md) | System performance data that was collected during profiling indicate a significant proportion of the memory for.NET Framework objects was reclaimed in generation 1 of garbage collection compared to generation 0 data collection. |
 | [DA0022: High rate of Gen 2 garbage collections](../profiling/da0022-high-rate-of-gen-2-garbage-collections.md) | System performance data that was collected during profiling indicate a significant proportion of the memory for.NET Framework objects was reclaimed in generation 2 of garbage collection compared to generation 0 and generation 1 garbage collections. |