Fix overlocalization of language elements (#9209)

Author: sdwheeler

reference/5.1/Microsoft.PowerShell.Core/About/about_Language_Modes.md

@@ -2,6 +2,7 @@
 description: Explains language modes and their effect on PowerShell sessions.
 Locale: en-US
 ms.date: 08/03/2021
+no-loc: [FullLanguage, ConstrainedLanguage, RestrictedLanguage, NoLanguage]
 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_language_modes?view=powershell-5.1&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: about Language Modes
@@ -23,7 +24,7 @@ PowerShell supports the following language modes:
 - **RestrictedLanguage**
 - **NoLanguage**
 
-### WHAT IS A LANGUAGE MODE?
+### What is a language mode?
 
 The language mode determines the language elements that are permitted in the
 session.
@@ -44,13 +45,13 @@ language mode of the session. To specify the session configuration of a
 PSSession, use the ConfigurationName parameter of cmdlets that create a
 session.
 
-### LANGUAGE MODES
+### Language modes
 
 This section describes the language modes in PowerShell sessions.
 
-#### FULL LANGUAGE (FullLanguage)
+#### Full language (FullLanguage)
 
-The FullLanguage mode permits all language elements in the session.
+The **FullLanguage** mode permits all language elements in the session.
 FullLanguage is the default language mode for default sessions on all versions
 of Windows except for Windows RT.
 
@@ -79,7 +80,7 @@ permitted.
 
 #### No language (NoLanguage)
 
-NoLanguage mode can only be used through the API. NoLanguage mode means no
+**NoLanguage** mode can only be used through the API. NoLanguage mode means no
 script text of any form is permitted. This precludes the use of the
 **AddScript()** method which sends fragments of PowerShell script to be parsed
 and executed. You can only use **AddCommand()** and **AddParameter()** which
@@ -139,58 +140,58 @@ The features of **ConstrainedLanguage** mode are as follows:
   - **Scripting.FileSystemObject**
   - **VBScript.RegExp**
 
-The following types are permitted in ConstrainedLanguage mode. Users
+The following types are permitted in **ConstrainedLanguage** mode. Users
 can get properties, invoke methods, and convert objects to these types.
 
 Allowed Types:
 
-- AliasAttribute
-- AllowEmptyCollectionAttribute
-- AllowEmptyStringAttribute
-- AllowNullAttribute
-- Array
-- Bool
-- byte
-- char
-- CmdletBindingAttribute
-- DateTime
-- decimal
-- DirectoryEntry
-- DirectorySearcher
-- double
-- float
-- Guid
-- Hashtable
-- int
-- Int16
-- long
-- ManagementClass
-- ManagementObject
-- ManagementObjectSearcher
-- NullString
-- OutputTypeAttribute
-- ParameterAttribute
-- PSCredential
-- PSDefaultValueAttribute
-- PSListModifier
-- PSObject
-- PSPrimitiveDictionary
-- PSReference
-- PSTypeNameAttribute
-- Regex
-- SByte
-- string
-- SupportsWildcardsAttribute
-- SwitchParameter
-- System.Globalization.CultureInfo
-- System.Net.IPAddress
-- System.Net.Mail.MailAddress
-- System.Numerics.BigInteger
-- System.Security.SecureString
-- TimeSpan
-- UInt16
-- UInt32
-- UInt64
+- `[AliasAttribute]`
+- `[AllowEmptyCollectionAttribute]`
+- `[AllowEmptyStringAttribute]`
+- `[AllowNullAttribute]`
+- `[Array]`
+- `[Bool]`
+- `[byte]`
+- `[char]`
+- `[CmdletBindingAttribute]`
+- `[DateTime]`
+- `[decimal]`
+- `[DirectoryEntry]`
+- `[DirectorySearcher]`
+- `[double]`
+- `[float]`
+- `[Guid]`
+- `[Hashtable]`
+- `[int]`
+- `[Int16]`
+- `[long]`
+- `[ManagementClass]`
+- `[ManagementObject]`
+- `[ManagementObjectSearcher]`
+- `[NullString]`
+- `[OutputTypeAttribute]`
+- `[ParameterAttribute]`
+- `[PSCredential]`
+- `[PSDefaultValueAttribute]`
+- `[PSListModifier]`
+- `[PSObject]`
+- `[PSPrimitiveDictionary]`
+- `[PSReference]`
+- `[PSTypeNameAttribute]`
+- `[Regex]`
+- `[SByte]`
+- `[String]`
+- `[SupportsWildcardsAttribute]`
+- `[SwitchParameter]`
+- `[System.Globalization.CultureInfo]`
+- `[System.Net.IPAddress]`
+- `[System.Net.Mail.MailAddress]`
+- `[System.Numerics.BigInteger]`
+- `[System.Security.SecureString]`
+- `[TimeSpan]`
+- `[UInt16]`
+- `[UInt32]`
+- `[UInt64]`
 
 ### Finding the language mode of a session configuration
 
@@ -204,7 +205,7 @@ FullLanguage
 ```
 
 On other session configurations, you can find the language mode indirectly by
-finding the language mode of a session that is created by using the session
+finding the language mode of a session that is created using the session
 configuration.
 
 ### Finding the language mode of a session

reference/5.1/Microsoft.PowerShell.Core/About/about_Line_Editing.md

@@ -1,7 +1,7 @@
 ---
 description: Describes how to edit commands at the PowerShell command prompt.
 Locale: en-US
-ms.date: 07/10/2019
+ms.date: 09/12/2022
 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_line_editing?view=powershell-5.1&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: about Line Editing
@@ -27,16 +27,15 @@ continuation prompt. Press <kbd>Enter</kbd> to execute the command.
 
 ### Move left and right
 
-To move the cursor one character to the left, press the <kbd>Left arrow</kbd>.
+To move the cursor one character to the left, press the <kbd>LeftArrow</kbd>.
 
-To move the cursor one word to the left, press <kbd>Ctrl</kbd>+<kbd>Left
-arrow</kbd>.
+To move the cursor one word to the left, press
+<kbd>Ctrl</kbd>+<kbd>LeftArrow</kbd>.
 
-To move the cursor one character to the right, press the <kbd>Right
-arrow</kbd>.
+To move the cursor one character to the right, press the <kbd>RightArrow</kbd>.
 
-To move the cursor one word to the right, press <kbd>Ctrl</kbd>+<kbd>Right
-arrow</kbd>.
+To move the cursor one word to the right, press
+<kbd>Ctrl</kbd>+<kbd>RightArrow</kbd>.
 
 ### Move to a line's beginning or end
 

reference/5.1/Microsoft.PowerShell.Core/About/about_Numeric_Literals.md

@@ -1,7 +1,8 @@
 ---
 description: Both integer and real numeric literals can have type and multiplier suffixes.
 Locale: en-US
-ms.date: 11/15/2021
+ms.date: 09/12/2022
+no-loc: [482gb]
 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_numeric_literals?view=powershell-5.1&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: about Numeric Literals
@@ -20,12 +21,12 @@ Integer literals can have a type suffix and a multiplier suffix.
 
 | Suffix |       Meaning       |
 | ------ | ------------------- |
-| l      | long data type      |
-| kb     | kilobyte multiplier |
-| mb     | megabyte multiplier |
-| gb     | gigabyte multiplier |
-| tb     | terabyte multiplier |
-| pb     | petabyte multiplier |
+| `l`    | long data type      |
+| `kb`   | kilobyte multiplier |
+| `mb`   | megabyte multiplier |
+| `gb`   | gigabyte multiplier |
+| `tb`   | terabyte multiplier |
+| `Pb`   | petabyte multiplier |
 
 The type of an integer literal is determined by its value, the type suffix, and
 the numeric multiplier suffix.
@@ -62,12 +63,12 @@ Real literals can have a type suffix and a multiplier suffix.
 
 | Suffix |       Meaning       |
 | ------ | ------------------- |
-| d      | decimal data type   |
-| kb     | kilobyte multiplier |
-| mb     | megabyte multiplier |
-| gb     | gigabyte multiplier |
-| tb     | terabyte multiplier |
-| pb     | petabyte multiplier |
+| `d`    | decimal data type   |
+| `kb`   | kilobyte multiplier |
+| `mb`   | megabyte multiplier |
+| `gb`   | gigabyte multiplier |
+| `tb`   | terabyte multiplier |
+| `pb`   | petabyte multiplier |
 
 There are two kinds of real literal: double and decimal. These are indicated by
 the absence or presence, respectively, of decimal-type suffix. PowerShell does

reference/5.1/Microsoft.PowerShell.Core/About/about_Output_Streams.md

@@ -1,7 +1,8 @@
 ---
 description: Explains the availability and purpose of output streams in PowerShell.
 Locale: en-US
-ms.date: 12/13/2021
+ms.date: 09/12/2022
+no-loc: [Success, Error, Warning, Verbose, Debug, Information, Progress]
 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_output_streams?view=powershell-5.1&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: about Output Streams