just use runtime (#50277)

Author: gewarren

docs/framework/additional-apis/pos-for-net/pos-exception-handling.md

@@ -8,7 +8,7 @@ ms.custom: "pos-restored-from-archive"
 
 # POS Exception Handling (POS for .NET v1.14 SDK Documentation)
 
-Error handling in Microsoft Point of Service for .NET (POS for .NET) is built on the object-oriented model of throwing and catching exceptions. Different exceptions are thrown in response to run-time errors, and each exception contains information about the error that triggered it in the form of an <xref:Microsoft.PointOfService.ErrorCode>.
+Error handling in Microsoft Point of Service for .NET (POS for .NET) is built on the object-oriented model of throwing and catching exceptions. Different exceptions are thrown in response to runtime errors, and each exception contains information about the error that triggered it in the form of an <xref:Microsoft.PointOfService.ErrorCode>.
 
 The **ErrorCode** property of a thrown exception holds information about the cause of the error. Possible values for this property represent the full set of standard Unified Point Of Service (UnifiedPOS) error codes. For more information about the mapping between UnifiedPOS error codes and the POS for .NET **ErrorCode** values, see POS for .NET [Exception Classes](exception-classes.md).
 

docs/framework/app-domains/application-domains.md

@@ -85,7 +85,7 @@ Operating systems and runtime environments typically provide some form of isolat
 
 ## Application domains and threads
 
- An application domain forms an isolation boundary for security, versioning, reliability, and unloading of managed code. A thread is the operating system construct used by the common language runtime to execute code. At run time, all managed code is loaded into an application domain and is run by one or more managed threads.
+ An application domain forms an isolation boundary for security, versioning, reliability, and unloading of managed code. A thread is the operating system construct used by the common language runtime to execute code. At runtime, all managed code is loaded into an application domain and is run by one or more managed threads.
 
  There is not a one-to-one correlation between application domains and threads. Several threads can execute in a single application domain at any given time, and a particular thread is not confined to a single application domain. That is, threads are free to cross application domain boundaries; a new thread is not created for each application domain.
 

docs/framework/configure-apps/file-schema/runtime/bindingredirect-element.md

@@ -57,7 +57,7 @@ newVersion="new assembly version"/>
 
 ## Remarks
 
- When you build a .NET Framework application against a strong-named assembly, the application uses that version of the assembly at run time by default, even if a new version is available. However, you can configure the application to run against a newer version of the assembly. For details on how the runtime uses these files to determine which assembly version to use, see [How the Runtime Locates Assemblies](../../../deployment/how-the-runtime-locates-assemblies.md).
+ When you build a .NET Framework application against a strong-named assembly, the application uses that version of the assembly at runtime by default, even if a new version is available. However, you can configure the application to run against a newer version of the assembly. For details on how the runtime uses these files to determine which assembly version to use, see [How the Runtime Locates Assemblies](../../../deployment/how-the-runtime-locates-assemblies.md).
 
  You can redirect more than one assembly version by including multiple `bindingRedirect` elements in a `dependentAssembly` element. You can also redirect from a newer version to an older version of the assembly.
 

docs/framework/configure-apps/file-schema/runtime/gcconservememory-element.md

@@ -54,7 +54,7 @@ This setting was introduced in .NET Framework 4.8.
 ## See also
 
 - [Configure apps by using configuration files](../../index.md)
-- [Run-time settings schema](index.md)
+- [Runtime settings schema](index.md)
 - [Configuration file schema](../index.md)
 - [Fundamentals of garbage collection](../../../../standard/garbage-collection/fundamentals.md)
 - [NET Core runtime config options for GC](../../../../core/runtime-config/garbage-collector.md)

docs/framework/configure-apps/file-schema/runtime/gclohthreshold-element.md

@@ -51,7 +51,7 @@ This setting was introduced in .NET Framework 4.8.
 ## See also
 
 - [Configure apps by using configuration files](../../index.md)
-- [Run-time settings schema](index.md)
+- [Runtime settings schema](index.md)
 - [Configuration file schema](../index.md)
 - [Fundamentals of garbage collection](../../../../standard/garbage-collection/fundamentals.md)
 - [NET Core runtime config options for GC](../../../../core/runtime-config/garbage-collector.md)

docs/framework/configure-apps/file-schema/runtime/index.md

@@ -114,7 +114,7 @@ Runtime settings are used by the common language runtime to configure applicatio
 |[\<memoryCache>](memorycache-element-cache-settings.md)|Defines an element that is used to configure a cache that is based on the <xref:System.Runtime.Caching.MemoryCache> class.|
 |[\<namedCaches>](namedcaches-element-cache-settings.md)|Contains a collection of configuration settings for the `namedCache` instance.|
 |[\<NetFx40_LegacySecurityPolicy>](netfx40-legacysecuritypolicy-element.md)|Specifies whether the runtime uses legacy code access security (CAS) policy.|
-|[\<NetFx40_PInvokeStackResilience>](netfx40-pinvokestackresilience-element.md)|Specifies whether the runtime automatically fixes incorrect platform invoke declarations at run time, at the cost of slower transitions between managed and unmanaged code.|
+|[\<NetFx40_PInvokeStackResilience>](netfx40-pinvokestackresilience-element.md)|Specifies whether the runtime automatically fixes incorrect platform invoke declarations at runtime, at the cost of slower transitions between managed and unmanaged code.|
 |[\<NetFx45_CultureAwareComparerGetHashCode_LongStrings>](netfx45-cultureawarecomparergethashcode-longstrings-element.md)|Specifies whether the runtime uses a fixed amount of memory to calculate hash codes for the <xref:System.StringComparer.GetHashCode%2A?displayProperty=nameWithType> method.|
 |[\<PreferComInsteadOfManagedRemoting>](prefercominsteadofmanagedremoting-element.md)|Specifies that the runtime will use COM interop instead of remoting across application domain boundaries.|
 |[\<probing>](probing-element.md)|Specifies subdirectories that the runtime searches when loading assemblies.|

docs/framework/configure-apps/file-schema/runtime/netfx40-pinvokestackresilience-element.md

@@ -9,7 +9,7 @@ ms.assetid: 39fb1588-72a4-4479-af74-0605233b68bd
 ---
 # `<NetFx40_PInvokeStackResilience>` Element
 
-Specifies whether the runtime automatically fixes incorrect platform invoke declarations at run time, at the cost of slower transitions between managed and unmanaged code.
+Specifies whether the runtime automatically fixes incorrect platform invoke declarations at runtime, at the cost of slower transitions between managed and unmanaged code.
 
 [**\<configuration>**](../configuration-element.md)\
 &nbsp;&nbsp;[**\<runtime>**](runtime-element.md)\
@@ -29,7 +29,7 @@ The following sections describe attributes, child elements, and parent elements.
 
 |Attribute|Description|
 |---------------|-----------------|
-|`enabled`|Required attribute.<br /><br /> Specifies whether the runtime detects incorrect platform invoke declarations and automatically fixes the stack at run time on 32-bit platforms.|
+|`enabled`|Required attribute.<br /><br /> Specifies whether the runtime detects incorrect platform invoke declarations and automatically fixes the stack at runtime on 32-bit platforms.|
 
 ## enabled Attribute
 
@@ -51,7 +51,7 @@ None.
 
 ## Remarks
 
-This element enables you to trade faster interop marshalling for run-time resilience against incorrect platform invoke declarations.
+This element enables you to trade faster interop marshalling for runtime resilience against incorrect platform invoke declarations.
 
 Starting with the .NET Framework 4, a streamlined interop marshalling architecture provides a significant performance improvement for transitions from managed code to unmanaged code. In earlier versions of the .NET Framework, the marshalling layer detected incorrect platform invoke declarations on 32-bit platforms and automatically fixed the stack. The new marshalling architecture eliminates this step. As a result, transitions are very fast, but an incorrect platform invoke declaration can cause a program failure.
 

docs/framework/configure-apps/file-schema/runtime/runtime-element.md

@@ -68,7 +68,7 @@ None.
 |[\<legacyImpersonationPolicy>](legacyimpersonationpolicy-element.md)|Specifies that the Windows identity does not flow across asynchronous points, regardless of the flow settings for the execution context on the current thread.|
 |[\<loadfromRemoteSources>](loadfromremotesources-element.md)|Specifies whether assemblies from remote sources are loaded as full trust.|
 |[\<NetFx40_LegacySecurityPolicy>](netfx40-legacysecuritypolicy-element.md)|Specifies whether the runtime uses legacy code access security (CAS) policy.|
-|[\<NetFx40_PInvokeStackResilience>](netfx40-pinvokestackresilience-element.md)|Specifies whether the runtime automatically fixes incorrect platform invoke declarations at run time, at the cost of slower transitions between managed and unmanaged code.|
+|[\<NetFx40_PInvokeStackResilience>](netfx40-pinvokestackresilience-element.md)|Specifies whether the runtime automatically fixes incorrect platform invoke declarations at runtime, at the cost of slower transitions between managed and unmanaged code.|
 |[\<NetFx45_CultureAwareComparerGetHashCode_LongStrings>](netfx45-cultureawarecomparergethashcode-longstrings-element.md)|Specifies whether the runtime uses a fixed amount of memory to calculate hash codes for the <xref:System.StringComparer.GetHashCode%2A?displayProperty=nameWithType> method.|
 |[\<PreferComInsteadOfRemoting>](prefercominsteadofmanagedremoting-element.md)|Specifies that the runtime will use COM interop instead of remoting across application domain boundaries.|
 |[\<relativeBindForResources>](relativebindforresources-element.md)|Optimizes the probe for satellite assemblies.|

docs/framework/configure-apps/file-schema/trace-debug/add-element-for-sharedlisteners.md

@@ -12,7 +12,7 @@ ms.assetid: 1595e1bc-2492-421f-8384-7f382eb8eb57
 ---
 # `<add>` Element for \<sharedListeners>
 
-Adds a listener to the `sharedListeners` collection. `sharedListeners` is a collection of listeners that any [\<source>](source-element.md) or [\<trace>](trace-element.md) can reference.  By default, listeners in the `sharedListeners` collection are not placed in a `Listeners` collection. They must be added by name to the [\<source>](source-element.md) or [\<trace>](trace-element.md). It is not possible to get the listeners in the `sharedListeners` collection in code at run time.
+Adds a listener to the `sharedListeners` collection. `sharedListeners` is a collection of listeners that any [\<source>](source-element.md) or [\<trace>](trace-element.md) can reference.  By default, listeners in the `sharedListeners` collection are not placed in a `Listeners` collection. They must be added by name to the [\<source>](source-element.md) or [\<trace>](trace-element.md). It is not possible to get the listeners in the `sharedListeners` collection in code at runtime.
 
 [**\<configuration>**](../configuration-element.md)\
 &nbsp;&nbsp;[**\<system.diagnostics>**](system-diagnostics-element.md)\

docs/framework/configure-apps/file-schema/trace-debug/sharedlisteners-element.md

@@ -15,7 +15,7 @@ ms.assetid: de200534-19dd-4156-86cf-c50521802c4c
 ---
 # `<sharedListeners>` Element
 
-Contains listeners that any source or trace element can reference.  These listeners do not receive any traces by default, and it is not possible to retrieve these listeners at run time. Listeners identified as shared listeners can be added to sources or traces by name.
+Contains listeners that any source or trace element can reference.  These listeners do not receive any traces by default, and it is not possible to retrieve these listeners at runtime. Listeners identified as shared listeners can be added to sources or traces by name.
 
 [**\<configuration>**](../configuration-element.md)
 &nbsp;&nbsp;[**\<system.diagnostics>**](system-diagnostics-element.md)