diff --git a/reference/5.1/Microsoft.PowerShell.Core/About/about_Run_With_PowerShell.md b/reference/5.1/Microsoft.PowerShell.Core/About/about_Run_With_PowerShell.md
index 64977b4e726..1fb41931d24 100644
--- a/reference/5.1/Microsoft.PowerShell.Core/About/about_Run_With_PowerShell.md
+++ b/reference/5.1/Microsoft.PowerShell.Core/About/about_Run_With_PowerShell.md
@@ -1,7 +1,7 @@
 ---
 description: Explains how to use the Run with PowerShell feature to run a script from a file system drive.
 Locale: en-US
-ms.date: 01/03/2018
+ms.date: 10/23/2023
 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_run_with_powershell?view=powershell-5.1&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: about Run With PowerShell
@@ -11,27 +11,25 @@ title: about Run With PowerShell
 
 ## Short description
 
-Explains how to use the "Run with PowerShell" feature to run a script from a
+Explains how to use the **Run with PowerShell** feature to run a script from a
 file system drive.
 
 ## Long description
 
-Beginning in Windows PowerShell 3.0, you can use the "Run with PowerShell"
-feature to run scripts from File Explorer in Windows 8 and Windows Server 2012
-and from Windows Explorer in earlier versions of Windows.
+Beginning in Windows PowerShell 3.0, you can use the **Run with PowerShell**
+feature to run scripts from File Explorer. The **Run with PowerShell** feature
+is designed to run scripts that don't have required parameters and don't return
+output to the command prompt.
 
-The "Run with PowerShell" feature is designed to run scripts that do not have
-required parameters and do not return output to the command prompt.
+When you use the **Run with PowerShell** feature, the Windows PowerShell
+console window appears only briefly, if at all. You can't interact with it.
 
-When you use the "Run with PowerShell" feature, the Windows PowerShell console
-window appears only briefly, if at all. You cannot interact with it.
+To use the **Run with PowerShell** feature:
 
-To use the "Run with PowerShell" feature:
+In File Explorer (or Windows Explorer), right-click the script filename and
+then select **Run with PowerShell**.
 
-In File Explorer (or Windows Explorer), right-click the script file name and
-then select "Run with PowerShell".
-
-The "Run with PowerShell" feature starts a Windows PowerShell session that has
+The **Run with PowerShell** feature starts a Windows PowerShell session that has
 an execution policy of Bypass, runs the script, and closes the session.
 
 It runs a command that has the following format:
@@ -40,22 +38,28 @@ It runs a command that has the following format:
 PowerShell.exe -File <FileName> -ExecutionPolicy Bypass
 ```
 
-"Run with PowerShell" sets the Bypass execution policy only for the session
+**Run with PowerShell** sets the Bypass execution policy only for the session
 (the current instance of the PowerShell process) in which the script runs.
-This feature does not change the execution policy for the computer or the
+This feature doesn't change the execution policy for the computer or the
 user.
 
-The "Run with PowerShell" feature is affected only by the AllSigned execution
+The **Run with PowerShell** feature is affected only by the AllSigned execution
 policy. If the AllSigned execution policy is effective for the computer or the
-user, "Run with PowerShell" runs only signed scripts. "Run with PowerShell" is
-not affected by any other execution policy. For more information, see
-[about_Execution_Policies](about_Execution_Policies.md).
+user, **Run with PowerShell** runs only signed scripts. **Run with PowerShell**
+is not affected by any other execution policy. For more information, see
+[about_Execution_Policies][01].
 
-Troubleshooting Note: Run with PowerShell command might prompt you to confirm
-the execution policy change.
+> [!NOTE]
+> **Run with PowerShell** feature might prompt you to confirm the execution
+> policy change.
 
 ## See also
 
-- [about_Execution_Policies](about_Execution_Policies.md)
-- [about_Group_Policy_Settings](about_Group_Policy_Settings.md)
-- [about_Scripts](about_Scripts.md)
+- [about_Execution_Policies][01]
+- [about_Group_Policy_Settings][02]
+- [about_Scripts][03]
+
+<!-- link references -->
+[01]: about_Execution_Policies.md
+[02]: about_Group_Policy_Settings.md
+[03]: about_Scripts.md
diff --git a/reference/5.1/Microsoft.PowerShell.Core/About/about_Signing.md b/reference/5.1/Microsoft.PowerShell.Core/About/about_Signing.md
index dd3fec8e0af..579e920caf1 100644
--- a/reference/5.1/Microsoft.PowerShell.Core/About/about_Signing.md
+++ b/reference/5.1/Microsoft.PowerShell.Core/About/about_Signing.md
@@ -1,7 +1,7 @@
 ---
 description: Explains how to sign scripts so that they comply with the PowerShell execution policies.
 Locale: en-US
-ms.date: 06/05/2023
+ms.date: 10/23/2023
 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_signing?view=powershell-5.1&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: about Signing
@@ -140,9 +140,8 @@ topic.
 ## Create a self-signed certificate
 
 To create a self-signed certificate, use the [New-SelfSignedCertificate][04]
-cmdlet in the PKI module. This module is introduced in PowerShell 3.0 and is
-included in Windows 8 and Windows Server 2012. For more information, see the
-help topic for the `New-SelfSignedCertificate` cmdlet.
+cmdlet in the PKI module. This module is introduced in PowerShell 3.0. For more
+information, see the help topic for the `New-SelfSignedCertificate` cmdlet.
 
 ```powershell
 $params = @{
diff --git a/reference/5.1/Microsoft.PowerShell.Core/About/about_Windows_PowerShell_ISE.md b/reference/5.1/Microsoft.PowerShell.Core/About/about_Windows_PowerShell_ISE.md
index adc83b9ca4e..143aa8a4178 100644
--- a/reference/5.1/Microsoft.PowerShell.Core/About/about_Windows_PowerShell_ISE.md
+++ b/reference/5.1/Microsoft.PowerShell.Core/About/about_Windows_PowerShell_ISE.md
@@ -48,16 +48,9 @@ Windows PowerShell ISE introduces two new features in Windows PowerShell 4.0.
 Windows PowerShell ISE is installed, enabled, and ready to use in all
 supported versions of Windows.
 
-- In Windows 8.1, Windows 8, Windows Server 2012 R2, and Windows Server 2012,
-  on the Start screen, type PowerShell_ISE, and then click PowerShell_ISE or
+- In the Start menu, type PowerShell_ISE, and then click PowerShell_ISE or
   Windows PowerShell ISE.
 
-- In Windows Server 2012 R2 and Windows Server 2012, in Server Manager, on the
-  Tools menu, click Windows PowerShell ISE.
-
-- In earlier versions of Windows, click Start, All Programs, Accessories,
-  Windows PowerShell, and then click Windows PowerShell ISE.
-
 - In a Windows PowerShell console, Cmd.exe, or the Run or Search box in
   Windows, type "PowerShell_ise.exe". You can also use the command-line
   parameters, including the NoProfile switch. For more information, see
diff --git a/reference/5.1/Microsoft.PowerShell.Core/About/about_Windows_Powershell_5.1.md b/reference/5.1/Microsoft.PowerShell.Core/About/about_Windows_Powershell_5.1.md
index 138c5615dab..2fb66486e00 100644
--- a/reference/5.1/Microsoft.PowerShell.Core/About/about_Windows_Powershell_5.1.md
+++ b/reference/5.1/Microsoft.PowerShell.Core/About/about_Windows_Powershell_5.1.md
@@ -1,7 +1,7 @@
 ---
 description: Describes new features that are included in Windows PowerShell 5.1.
 Locale: en-US
-ms.date: 01/17/2018
+ms.date: 10/23/2023
 online version: https://learn.microsoft.com/powershell/module/about_windows_powershell_5.1?view=powershell-5.1&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: about Windows Powershell 5.1
@@ -34,23 +34,21 @@ work in Windows PowerShell 5.1 without changes.
   from the Pull Server and when using PowerShellGet cmdlets
 - Responses to a number of user requests and issues
 
-Windows PowerShell 5.1 is installed by default on Windows Server version 2016 and higher and Windows
-client version 10 and higher.
+Windows PowerShell 5.1 is installed by default on Windows Server version 2016
+and higher and Windows client version 10 and higher.
 
-To install Windows PowerShell 5.1 on Windows Server 2012 R2, Windows 8.1 Enterprise, or Windows 8.1
-Pro, see [Install and Configure WMF 5.1](/powershell/scripting/wmf/setup/install-configure). Be sure
-to read the download details, and meet all system requirements, before you install Windows
-Management Framework 5.1.
+To install Windows PowerShell 5.1 on older versions of Windows, see
+[Install and Configure WMF 5.1][09]. Be sure to read the download details, and
+meet all system requirements, before you install Windows Management Framework
+5.1.
 
 You can also read about changes to Windows PowerShell 5.1 in
-[What's New in Windows PowerShell](/powershell/scripting/windows-powershell/whats-new/what-s-new-in-windows-powershell-50).
-
-## New Scenarios and Features in WMF 5.1
-
-> Note: This information is preliminary and subject to change.
+[What's New in Windows PowerShell][08].
 
 ### PowerShell Editions
-Starting with version 5.1, PowerShell is available in different editions which denote varying feature sets and platform compatibility.
+
+Starting with version 5.1, PowerShell is available in different editions which
+denote varying feature sets and platform compatibility.
 
 - **Desktop Edition:** Built on .NET Framework and provides compatibility with
   scripts and modules targeting versions of PowerShell running on full footprint
@@ -61,20 +59,19 @@ Starting with version 5.1, PowerShell is available in different editions which d
 
 **Learn more about using PowerShell Editions**
 
-- [Determine running edition of PowerShell using $PSVersionTable](/powershell/module/microsoft.powershell.core/about/about_automatic_variables)
-- [Filter Get-Module results by CompatiblePSEditions using PSEdition parameter](/powershell/module/microsoft.powershell.core/get-module)
-- [Prevent script execution unless run on a compatible edition of PowerShell](/powershell/gallery/concepts/script-psedition-support)
-- [Declare a module's compatibility to specific PowerShell versions](/powershell/gallery/concepts/module-psedition-support)
+- [Determine running edition of PowerShell using $PSVersionTable][04]
+- [Filter Get-Module results by CompatiblePSEditions using PSEdition parameter][05]
+- [Prevent script execution unless run on a compatible edition of PowerShell][03]
+- [Declare a module's compatibility to specific PowerShell versions][02]
 
 ### Catalog Cmdlets
 
-Two new cmdlets have been added in the
-[Microsoft.PowerShell.Security](/previous-versions/windows/powershell-scripting/hh847877(v=wps.640))
-module; these generate and validate Windows catalog files.
+Two new cmdlets have been added in the [Microsoft.PowerShell.Security][10]
+module. These cmdlets generate and validate Windows catalog files.
 
 #### New-FileCatalog
 
-New-FileCatalog creates a Windows catalog file for set of folders and files.
+`New-FileCatalog` creates a Windows catalog file for set of folders and files.
 This catalog file contains hashes for all files in specified paths. Users can
 distribute the set of folders along with corresponding catalog file
 representing those folders. This information is useful to validate whether any
@@ -86,19 +83,15 @@ New-FileCatalog [-CatalogFilePath] <string> [[-Path] <string[]>]
 ```
 
 Catalog versions 1 and 2 are supported. Version 1 uses the SHA1 hashing
-algorithm to create file hashes; version 2 uses SHA256. Catalog version 2 is
-not supported on *Windows Server 2008 R2* or *Windows 7*. You should use
-catalog version 2 on *Windows 8*, *Windows Server 2012*, and later operating
-systems.
+algorithm to create file hashes; version 2 uses SHA256. You should use catalog
+version 2.
 
 To verify the integrity of catalog file (Pester.cat in above example), sign it
-using
-[Set-AuthenticodeSignature](/powershell/module/microsoft.powershell.security/set-authenticodesignature)
-cmdlet.
+using [Set-AuthenticodeSignature][07] cmdlet.
 
 #### Test-FileCatalog
 
-Test-FileCatalog validates the catalog representing a set of folders.
+`Test-FileCatalog` validates the catalog representing a set of folders.
 
 ```
 Test-FileCatalog [-Detailed] [-FilesToSkip <String[]>]
@@ -106,38 +99,37 @@ Test-FileCatalog [-Detailed] [-FilesToSkip <String[]>]
  [-WhatIf] [-Confirm] [<CommonParameters>]
 ```
 
-This cmdlet compares all the files hashes and their relative paths found in
-*catalog* with ones on *disk*. If it detects any mismatch between file hashes
-and paths it returns the status as *ValidationFailed*. Users can retrieve all
-this information by using the *-Detailed* parameter. It also displays signing
-status of catalog in *Signature* property which is equivalent to calling
-[Get-AuthenticodeSignature](/powershell/module/microsoft.powershell.security/get-authenticodesignature)
-cmdlet on the catalog file. Users can also skip any file during validation by
-using the *-FilesToSkip* parameter.
+This cmdlet compares all file hashes and their relative paths found in a
+_catalog_ with files on _disk_. If it detects any mismatch between file hashes
+and paths it returns the status as `ValidationFailed`. Users can retrieve all
+this information using the **Detailed** parameter. It also displays signing
+status of catalog in **Signature** property, which is equivalent to calling
+[Get-AuthenticodeSignature][06] cmdlet on the catalog file. Users can also skip
+any file during validation using the **FilesToSkip** parameter.
 
 ### Module Analysis Cache
 
-Starting with WMF 5.1, PowerShell provides control over the file that is used
+Starting with WMF 5.1, PowerShell provides control over the file that's used
 to cache data about a module, such as the commands it exports.
 
 By default, this cache is stored in the file
 `${env:LOCALAPPDATA}\Microsoft\Windows\PowerShell\ModuleAnalysisCache`. The
-cache is typically read at startup while searching for a command and is
-written on a background thread sometime after a module is imported.
+cache is typically read at startup while searching for a command and is written
+on a background thread sometime after a module is imported.
 
 To change the default location of the cache, set the
 `$env:PSModuleAnalysisCachePath` environment variable before starting
-PowerShell. Changes to this environment variable will only affect children
-processes. The value should name a full path (including filename) that
-PowerShell has permission to create and write files. To disable the file
-cache, set this value to an invalid location, for example:
+PowerShell. Changes to this environment variable only affect child processes.
+The value should name a full path (including filename) that PowerShell has
+permission to create and write files. To disable the file cache, set this value
+to an invalid location, for example:
 
 ```powershell
 $env:PSModuleAnalysisCachePath = 'nul'
 ```
 
-This sets the path to an invalid device. If PowerShell can't write to the
-path, no error is returned, but you can see error reporting by using a tracer:
+This sets the path to an invalid device. If PowerShell can't write to the path,
+no error is returned, but you can see error reporting using a tracer:
 
 ```powershell
 Trace-Command -PSHost -Name Modules -Expression {
@@ -145,44 +137,53 @@ Trace-Command -PSHost -Name Modules -Expression {
 }
 ```
 
-When writing out the cache, PowerShell will check for modules that no longer
-exist to avoid an unnecessarily large cache. Sometimes these checks are not
-desirable, in which case you can turn them off by setting:
+When writing out the cache, PowerShell checks for modules that no longer exist
+to avoid an unnecessarily large cache. You can disable the checks using the
+following setting:
 
 ```powershell
 $env:PSDisableModuleAnalysisCacheCleanup = 1
 ```
 
-Setting this environment variable will take effect immediately in the current
+Setting this environment variable takes effect immediately in the current
 process.
 
 ### Specifying module version
 
 In WMF 5.1, `using module` behaves the same way as other module-related
-constructions in PowerShell. Previously, you had no way to specify a
-particular module version; if there were multiple versions present, this
-resulted in an error.
+constructions in PowerShell. Previously, you had no way to specify a particular
+module version. If there were multiple versions present, this resulted in an
+error.
 
 In WMF 5.1:
 
-* You can use [ModuleSpecification Constructor (Hashtable)](/dotnet/api/microsoft.powershell.commands.modulespecification.-ctor).
-  This hash table has the same format as `Get-Module -FullyQualifiedName`.
+- You can use [ModuleSpecification Constructor (Hashtable)][01]. This hash
+  table has the same format as `Get-Module -FullyQualifiedName`.
 
   **Example:** `using module @{ModuleName = 'PSReadLine'; RequiredVersion = '1.1'}`
 
-* If there are multiple versions of the module, PowerShell uses the **same
-  resolution logic** as `Import-Module` and doesn't return an error--the same
-  behavior as `Import-Module` and `Import-DscResource`.
+- If there are multiple versions of the module, PowerShell uses the **same
+  resolution logic** as `Import-Module` and doesn't return an error.
 
 ### Improvements to Pester
 
 In WMF 5.1, the version of Pester that ships with PowerShell has been updated
-from 3.3.5 to 3.4.0, with the addition of GitHub [PR# 484](https://github.com/pester/Pester/pull/484),
-which enables better behavior for Pester on Nano Server.
-
-You can review the changes in versions 3.3.5 to 3.4.0 by inspecting the
-[CHANGELOG](https://github.com/pester/Pester/blob/main/docs/CHANGELOG.md) in the GitHub repository.
+from 3.3.5 to 3.4.0. You can review the changes in versions 3.3.5 to 3.4.0 by
+inspecting the [CHANGELOG][11] in the GitHub repository.
 
 ## KEYWORDS
 
 What's New in Windows PowerShell 5.1
+
+<!-- link references -->
+[01]: /dotnet/api/microsoft.powershell.commands.modulespecification.-ctor
+[02]: /powershell/gallery/concepts/module-psedition-support
+[03]: /powershell/gallery/concepts/script-psedition-support
+[04]: /powershell/module/microsoft.powershell.core/about/about_automatic_variables
+[05]: /powershell/module/microsoft.powershell.core/get-module
+[06]: /powershell/module/microsoft.powershell.security/get-authenticodesignature
+[07]: /powershell/module/microsoft.powershell.security/set-authenticodesignature
+[08]: /powershell/scripting/windows-powershell/whats-new/what-s-new-in-windows-powershell-50
+[09]: /powershell/scripting/wmf/setup/install-configure
+[10]: /previous-versions/windows/powershell-scripting/hh847877(v=wps.640)
+[11]: https://github.com/pester/Pester/blob/main/docs/CHANGELOG.md
diff --git a/reference/5.1/Microsoft.PowerShell.Management/Show-ControlPanelItem.md b/reference/5.1/Microsoft.PowerShell.Management/Show-ControlPanelItem.md
index a8d815497da..c52618e11eb 100644
--- a/reference/5.1/Microsoft.PowerShell.Management/Show-ControlPanelItem.md
+++ b/reference/5.1/Microsoft.PowerShell.Management/Show-ControlPanelItem.md
@@ -43,8 +43,7 @@ user interface. You can pipe control panel items from the `Get-ControlPanelItem`
 computers that do not have **Control Panel** or **File Explorer**, `Show-ControlPanelItem` searches
 only control panel items that can open without these components.
 
-This cmdlet was introduced in Windows PowerShell 3.0 and works on Windows 8, Windows Server 2012,
-and higher versions.
+This cmdlet was introduced in Windows PowerShell 3.0.
 
 ## EXAMPLES
 
diff --git a/reference/5.1/Microsoft.PowerShell.Security/New-FileCatalog.md b/reference/5.1/Microsoft.PowerShell.Security/New-FileCatalog.md
index e70cc73fb35..593b4cde044 100644
--- a/reference/5.1/Microsoft.PowerShell.Security/New-FileCatalog.md
+++ b/reference/5.1/Microsoft.PowerShell.Security/New-FileCatalog.md
@@ -2,7 +2,7 @@
 external help file: Microsoft.PowerShell.Security.dll-Help.xml
 Locale: en-US
 Module Name: Microsoft.PowerShell.Security
-ms.date: 12/12/2022
+ms.date: 10/23/2023
 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.security/new-filecatalog?view=powershell-5.1&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: New-FileCatalog
@@ -29,9 +29,7 @@ paths. Users can then distribute the catalog with their files so that users can
 changes have been made to the folders since catalog creation time.
 
 Catalog versions 1 and 2 are supported. Version 1 uses the (deprecated) SHA1 hashing algorithm to
-create file hashes, and version 2 uses SHA256. Catalog version 2 is not supported on Windows Server
-2008 R2 or Windows 7. You should use catalog version 2 on Windows 8, Windows Server 2012, and later
-operating systems.
+create file hashes, and version 2 uses SHA256.
 
 ## EXAMPLES
 
diff --git a/reference/5.1/Microsoft.PowerShell.Security/Set-Acl.md b/reference/5.1/Microsoft.PowerShell.Security/Set-Acl.md
index 12af7e0a386..29c26ba521a 100644
--- a/reference/5.1/Microsoft.PowerShell.Security/Set-Acl.md
+++ b/reference/5.1/Microsoft.PowerShell.Security/Set-Acl.md
@@ -2,7 +2,7 @@
 external help file: Microsoft.PowerShell.Security.dll-Help.xml
 Locale: en-US
 Module Name: Microsoft.PowerShell.Security
-ms.date: 12/12/2022
+ms.date: 10/23/2023
 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.security/set-acl?view=powershell-5.1&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: Set-Acl
@@ -205,8 +205,9 @@ Accept wildcard characters: False
 Establishes or changes the central access policy of the item.
 Enter the CAP ID or friendly name of a central access policy on the computer.
 
-Beginning in Windows Server 2012, administrators can use Active Directory and Group Policy to set central access policies for users and groups.
-For more information, see [Dynamic Access Control: Scenario Overview](/windows-server/identity/solution-guides/dynamic-access-control--scenario-overview).
+Beginning in Windows Server 2012, administrators can use Active Directory and Group Policy to set
+central access policies for users and groups. For more information, see
+[Dynamic Access Control: Scenario Overview](/windows-server/identity/solution-guides/dynamic-access-control--scenario-overview).
 
 This parameter was introduced in Windows PowerShell 3.0.
 
diff --git a/reference/7.2/Microsoft.PowerShell.Core/About/about_Run_With_PowerShell.md b/reference/7.2/Microsoft.PowerShell.Core/About/about_Run_With_PowerShell.md
index 57885bc0581..156c4e312a3 100644
--- a/reference/7.2/Microsoft.PowerShell.Core/About/about_Run_With_PowerShell.md
+++ b/reference/7.2/Microsoft.PowerShell.Core/About/about_Run_With_PowerShell.md
@@ -1,35 +1,35 @@
 ---
 description: Explains how to use the Run with PowerShell feature to run a script from a file system drive.
 Locale: en-US
-ms.date: 01/03/2018
+ms.date: 10/23/2023
 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_run_with_powershell?view=powershell-7.2&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: about Run With PowerShell
 ---
+
 # about_Run_With_PowerShell
 
 ## Short description
-Explains how to use the "Run with PowerShell" feature to run a script from a
+
+Explains how to use the **Run with PowerShell** feature to run a script from a
 file system drive.
 
 ## Long description
 
-Beginning in Windows PowerShell 3.0, you can use the "Run with PowerShell"
-feature to run scripts from File Explorer in Windows 8 and Windows Server 2012
-and from Windows Explorer in earlier versions of Windows.
+Beginning in Windows PowerShell 3.0, you can use the **Run with PowerShell**
+feature to run scripts from File Explorer. The **Run with PowerShell** feature
+is designed to run scripts that don't have required parameters and don't return
+output to the command prompt.
 
-The "Run with PowerShell" feature is designed to run scripts that do not have
-required parameters and do not return output to the command prompt.
+When you use the **Run with PowerShell** feature, the Windows PowerShell
+console window appears only briefly, if at all. You can't interact with it.
 
-When you use the "Run with PowerShell" feature, the PowerShell console
-window appears only briefly, if at all. You cannot interact with it.
+To use the **Run with PowerShell** feature:
 
-To use the "Run with PowerShell" feature:
+In File Explorer (or Windows Explorer), right-click the script filename and
+then select **Run with PowerShell**.
 
-In File Explorer (or Windows Explorer), right-click the script file name and
-then select "Run with PowerShell".
-
-The "Run with PowerShell" feature starts a PowerShell session that has
+The **Run with PowerShell** feature starts a Windows PowerShell session that has
 an execution policy of Bypass, runs the script, and closes the session.
 
 It runs a command that has the following format:
@@ -38,22 +38,28 @@ It runs a command that has the following format:
 PowerShell.exe -File <FileName> -ExecutionPolicy Bypass
 ```
 
-"Run with PowerShell" sets the Bypass execution policy only for the session
+**Run with PowerShell** sets the Bypass execution policy only for the session
 (the current instance of the PowerShell process) in which the script runs.
-This feature does not change the execution policy for the computer or the
+This feature doesn't change the execution policy for the computer or the
 user.
 
-The "Run with PowerShell" feature is affected only by the AllSigned execution
+The **Run with PowerShell** feature is affected only by the AllSigned execution
 policy. If the AllSigned execution policy is effective for the computer or the
-user, "Run with PowerShell" runs only signed scripts. "Run with PowerShell" is
-not affected by any other execution policy. For more information, see
-[about_Execution_Policies](about_Execution_Policies.md).
+user, **Run with PowerShell** runs only signed scripts. **Run with PowerShell**
+is not affected by any other execution policy. For more information, see
+[about_Execution_Policies][01].
 
-Troubleshooting Note: Run with PowerShell command might prompt you to confirm
-the execution policy change.
+> [!NOTE]
+> **Run with PowerShell** feature might prompt you to confirm the execution
+> policy change.
 
 ## See also
 
-- [about_Execution_Policies](about_Execution_Policies.md)
-- [about_Group_Policy_Settings](about_Group_Policy_Settings.md)
-- [about_Scripts](about_Scripts.md)
+- [about_Execution_Policies][01]
+- [about_Group_Policy_Settings][02]
+- [about_Scripts][03]
+
+<!-- link references -->
+[01]: about_Execution_Policies.md
+[02]: about_Group_Policy_Settings.md
+[03]: about_Scripts.md
diff --git a/reference/7.2/Microsoft.PowerShell.Core/About/about_Signing.md b/reference/7.2/Microsoft.PowerShell.Core/About/about_Signing.md
index ebabb2c6e69..374388d8b63 100644
--- a/reference/7.2/Microsoft.PowerShell.Core/About/about_Signing.md
+++ b/reference/7.2/Microsoft.PowerShell.Core/About/about_Signing.md
@@ -1,7 +1,7 @@
 ---
 description: Explains how to sign scripts so that they comply with the PowerShell execution policies.
 Locale: en-US
-ms.date: 06/05/2023
+ms.date: 10/23/2023
 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_signing?view=powershell-7.2&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: about Signing
@@ -142,9 +142,8 @@ topic.
 ## Create a self-signed certificate
 
 To create a self-signed certificate, use the [New-SelfSignedCertificate][04]
-cmdlet in the PKI module. This module is introduced in PowerShell 3.0 and is
-included in Windows 8 and Windows Server 2012. For more information, see the
-help topic for the `New-SelfSignedCertificate` cmdlet.
+cmdlet in the PKI module. This module is introduced in PowerShell 3.0. For more
+information, see the help topic for the `New-SelfSignedCertificate` cmdlet.
 
 ```powershell
 $params = @{
diff --git a/reference/7.2/Microsoft.PowerShell.Security/New-FileCatalog.md b/reference/7.2/Microsoft.PowerShell.Security/New-FileCatalog.md
index f2bb653253d..500179e77d6 100644
--- a/reference/7.2/Microsoft.PowerShell.Security/New-FileCatalog.md
+++ b/reference/7.2/Microsoft.PowerShell.Security/New-FileCatalog.md
@@ -2,7 +2,7 @@
 external help file: Microsoft.PowerShell.Security.dll-Help.xml
 Locale: en-US
 Module Name: Microsoft.PowerShell.Security
-ms.date: 12/12/2022
+ms.date: 10/23/2023
 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.security/new-filecatalog?view=powershell-7.2&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: New-FileCatalog
@@ -31,9 +31,7 @@ paths. Users can then distribute the catalog with their files so that users can
 changes have been made to the folders since catalog creation time.
 
 Catalog versions 1 and 2 are supported. Version 1 uses the (deprecated) SHA1 hashing algorithm to
-create file hashes, and version 2 uses SHA256. Catalog version 2 is not supported on Windows Server
-2008 R2 or Windows 7. You should use catalog version 2 on Windows 8, Windows Server 2012, and later
-operating systems.
+create file hashes, and version 2 uses SHA256.
 
 ## EXAMPLES
 
diff --git a/reference/7.2/Microsoft.PowerShell.Security/Set-Acl.md b/reference/7.2/Microsoft.PowerShell.Security/Set-Acl.md
index cde333d0206..b4aa4240b45 100644
--- a/reference/7.2/Microsoft.PowerShell.Security/Set-Acl.md
+++ b/reference/7.2/Microsoft.PowerShell.Security/Set-Acl.md
@@ -2,7 +2,7 @@
 external help file: Microsoft.PowerShell.Security.dll-Help.xml
 Locale: en-US
 Module Name: Microsoft.PowerShell.Security
-ms.date: 12/12/2022
+ms.date: 10/23/2023
 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.security/set-acl?view=powershell-7.2&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: Set-Acl
diff --git a/reference/7.3/Microsoft.PowerShell.Core/About/about_Run_With_PowerShell.md b/reference/7.3/Microsoft.PowerShell.Core/About/about_Run_With_PowerShell.md
index 6712829022a..13f24a27753 100644
--- a/reference/7.3/Microsoft.PowerShell.Core/About/about_Run_With_PowerShell.md
+++ b/reference/7.3/Microsoft.PowerShell.Core/About/about_Run_With_PowerShell.md
@@ -1,35 +1,35 @@
 ---
 description: Explains how to use the Run with PowerShell feature to run a script from a file system drive.
 Locale: en-US
-ms.date: 01/03/2018
+ms.date: 10/23/2023
 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_run_with_powershell?view=powershell-7.3&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: about Run With PowerShell
 ---
+
 # about_Run_With_PowerShell
 
 ## Short description
-Explains how to use the "Run with PowerShell" feature to run a script from a
+
+Explains how to use the **Run with PowerShell** feature to run a script from a
 file system drive.
 
 ## Long description
 
-Beginning in Windows PowerShell 3.0, you can use the "Run with PowerShell"
-feature to run scripts from File Explorer in Windows 8 and Windows Server 2012
-and from Windows Explorer in earlier versions of Windows.
+Beginning in Windows PowerShell 3.0, you can use the **Run with PowerShell**
+feature to run scripts from File Explorer. The **Run with PowerShell** feature
+is designed to run scripts that don't have required parameters and don't return
+output to the command prompt.
 
-The "Run with PowerShell" feature is designed to run scripts that do not have
-required parameters and do not return output to the command prompt.
+When you use the **Run with PowerShell** feature, the Windows PowerShell
+console window appears only briefly, if at all. You can't interact with it.
 
-When you use the "Run with PowerShell" feature, the PowerShell console
-window appears only briefly, if at all. You cannot interact with it.
+To use the **Run with PowerShell** feature:
 
-To use the "Run with PowerShell" feature:
+In File Explorer (or Windows Explorer), right-click the script filename and
+then select **Run with PowerShell**.
 
-In File Explorer (or Windows Explorer), right-click the script file name and
-then select "Run with PowerShell".
-
-The "Run with PowerShell" feature starts a PowerShell session that has
+The **Run with PowerShell** feature starts a Windows PowerShell session that has
 an execution policy of Bypass, runs the script, and closes the session.
 
 It runs a command that has the following format:
@@ -38,22 +38,28 @@ It runs a command that has the following format:
 PowerShell.exe -File <FileName> -ExecutionPolicy Bypass
 ```
 
-"Run with PowerShell" sets the Bypass execution policy only for the session
+**Run with PowerShell** sets the Bypass execution policy only for the session
 (the current instance of the PowerShell process) in which the script runs.
-This feature does not change the execution policy for the computer or the
+This feature doesn't change the execution policy for the computer or the
 user.
 
-The "Run with PowerShell" feature is affected only by the AllSigned execution
+The **Run with PowerShell** feature is affected only by the AllSigned execution
 policy. If the AllSigned execution policy is effective for the computer or the
-user, "Run with PowerShell" runs only signed scripts. "Run with PowerShell" is
-not affected by any other execution policy. For more information, see
-[about_Execution_Policies](about_Execution_Policies.md).
+user, **Run with PowerShell** runs only signed scripts. **Run with PowerShell**
+is not affected by any other execution policy. For more information, see
+[about_Execution_Policies][01].
 
-Troubleshooting Note: Run with PowerShell command might prompt you to confirm
-the execution policy change.
+> [!NOTE]
+> **Run with PowerShell** feature might prompt you to confirm the execution
+> policy change.
 
 ## See also
 
-- [about_Execution_Policies](about_Execution_Policies.md)
-- [about_Group_Policy_Settings](about_Group_Policy_Settings.md)
-- [about_Scripts](about_Scripts.md)
+- [about_Execution_Policies][01]
+- [about_Group_Policy_Settings][02]
+- [about_Scripts][03]
+
+<!-- link references -->
+[01]: about_Execution_Policies.md
+[02]: about_Group_Policy_Settings.md
+[03]: about_Scripts.md
diff --git a/reference/7.3/Microsoft.PowerShell.Core/About/about_Signing.md b/reference/7.3/Microsoft.PowerShell.Core/About/about_Signing.md
index 417f1788844..6d74bfc80dd 100644
--- a/reference/7.3/Microsoft.PowerShell.Core/About/about_Signing.md
+++ b/reference/7.3/Microsoft.PowerShell.Core/About/about_Signing.md
@@ -1,7 +1,7 @@
 ---
 description: Explains how to sign scripts so that they comply with the PowerShell execution policies.
 Locale: en-US
-ms.date: 06/05/2023
+ms.date: 10/23/2023
 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_signing?view=powershell-7.3&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: about Signing
@@ -142,9 +142,8 @@ topic.
 ## Create a self-signed certificate
 
 To create a self-signed certificate, use the [New-SelfSignedCertificate][04]
-cmdlet in the PKI module. This module is introduced in PowerShell 3.0 and is
-included in Windows 8 and Windows Server 2012. For more information, see the
-help topic for the `New-SelfSignedCertificate` cmdlet.
+cmdlet in the PKI module. This module is introduced in PowerShell 3.0. For more
+information, see the help topic for the `New-SelfSignedCertificate` cmdlet.
 
 ```powershell
 $params = @{
diff --git a/reference/7.3/Microsoft.PowerShell.Security/New-FileCatalog.md b/reference/7.3/Microsoft.PowerShell.Security/New-FileCatalog.md
index eab8c9ff7a8..26f0e663cb9 100644
--- a/reference/7.3/Microsoft.PowerShell.Security/New-FileCatalog.md
+++ b/reference/7.3/Microsoft.PowerShell.Security/New-FileCatalog.md
@@ -2,7 +2,7 @@
 external help file: Microsoft.PowerShell.Security.dll-Help.xml
 Locale: en-US
 Module Name: Microsoft.PowerShell.Security
-ms.date: 12/12/2022
+ms.date: 10/23/2023
 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.security/new-filecatalog?view=powershell-7.3&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: New-FileCatalog
@@ -31,9 +31,7 @@ paths. Users can then distribute the catalog with their files so that users can
 changes have been made to the folders since catalog creation time.
 
 Catalog versions 1 and 2 are supported. Version 1 uses the (deprecated) SHA1 hashing algorithm to
-create file hashes, and version 2 uses SHA256. Catalog version 2 is not supported on Windows Server
-2008 R2 or Windows 7. You should use catalog version 2 on Windows 8, Windows Server 2012, and later
-operating systems.
+create file hashes, and version 2 uses SHA256.
 
 ## EXAMPLES
 
diff --git a/reference/7.3/Microsoft.PowerShell.Security/Set-Acl.md b/reference/7.3/Microsoft.PowerShell.Security/Set-Acl.md
index c39821a0b44..dc41554f2fc 100644
--- a/reference/7.3/Microsoft.PowerShell.Security/Set-Acl.md
+++ b/reference/7.3/Microsoft.PowerShell.Security/Set-Acl.md
@@ -2,7 +2,7 @@
 external help file: Microsoft.PowerShell.Security.dll-Help.xml
 Locale: en-US
 Module Name: Microsoft.PowerShell.Security
-ms.date: 12/12/2022
+ms.date: 10/23/2023
 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.security/set-acl?view=powershell-7.3&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: Set-Acl
diff --git a/reference/7.4/Microsoft.PowerShell.Core/About/about_Run_With_PowerShell.md b/reference/7.4/Microsoft.PowerShell.Core/About/about_Run_With_PowerShell.md
index 7f6f1e52d23..6367d2ecf1c 100644
--- a/reference/7.4/Microsoft.PowerShell.Core/About/about_Run_With_PowerShell.md
+++ b/reference/7.4/Microsoft.PowerShell.Core/About/about_Run_With_PowerShell.md
@@ -1,35 +1,35 @@
 ---
 description: Explains how to use the Run with PowerShell feature to run a script from a file system drive.
 Locale: en-US
-ms.date: 01/03/2018
+ms.date: 10/23/2023
 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_run_with_powershell?view=powershell-7.4&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: about Run With PowerShell
 ---
+
 # about_Run_With_PowerShell
 
 ## Short description
-Explains how to use the "Run with PowerShell" feature to run a script from a
+
+Explains how to use the **Run with PowerShell** feature to run a script from a
 file system drive.
 
 ## Long description
 
-Beginning in Windows PowerShell 3.0, you can use the "Run with PowerShell"
-feature to run scripts from File Explorer in Windows 8 and Windows Server 2012
-and from Windows Explorer in earlier versions of Windows.
+Beginning in Windows PowerShell 3.0, you can use the **Run with PowerShell**
+feature to run scripts from File Explorer. The **Run with PowerShell** feature
+is designed to run scripts that don't have required parameters and don't return
+output to the command prompt.
 
-The "Run with PowerShell" feature is designed to run scripts that do not have
-required parameters and do not return output to the command prompt.
+When you use the **Run with PowerShell** feature, the Windows PowerShell
+console window appears only briefly, if at all. You can't interact with it.
 
-When you use the "Run with PowerShell" feature, the PowerShell console
-window appears only briefly, if at all. You cannot interact with it.
+To use the **Run with PowerShell** feature:
 
-To use the "Run with PowerShell" feature:
+In File Explorer (or Windows Explorer), right-click the script filename and
+then select **Run with PowerShell**.
 
-In File Explorer (or Windows Explorer), right-click the script file name and
-then select "Run with PowerShell".
-
-The "Run with PowerShell" feature starts a PowerShell session that has
+The **Run with PowerShell** feature starts a Windows PowerShell session that has
 an execution policy of Bypass, runs the script, and closes the session.
 
 It runs a command that has the following format:
@@ -38,22 +38,28 @@ It runs a command that has the following format:
 PowerShell.exe -File <FileName> -ExecutionPolicy Bypass
 ```
 
-"Run with PowerShell" sets the Bypass execution policy only for the session
+**Run with PowerShell** sets the Bypass execution policy only for the session
 (the current instance of the PowerShell process) in which the script runs.
-This feature does not change the execution policy for the computer or the
+This feature doesn't change the execution policy for the computer or the
 user.
 
-The "Run with PowerShell" feature is affected only by the AllSigned execution
+The **Run with PowerShell** feature is affected only by the AllSigned execution
 policy. If the AllSigned execution policy is effective for the computer or the
-user, "Run with PowerShell" runs only signed scripts. "Run with PowerShell" is
-not affected by any other execution policy. For more information, see
-[about_Execution_Policies](about_Execution_Policies.md).
+user, **Run with PowerShell** runs only signed scripts. **Run with PowerShell**
+is not affected by any other execution policy. For more information, see
+[about_Execution_Policies][01].
 
-Troubleshooting Note: Run with PowerShell command might prompt you to confirm
-the execution policy change.
+> [!NOTE]
+> **Run with PowerShell** feature might prompt you to confirm the execution
+> policy change.
 
 ## See also
 
-- [about_Execution_Policies](about_Execution_Policies.md)
-- [about_Group_Policy_Settings](about_Group_Policy_Settings.md)
-- [about_Scripts](about_Scripts.md)
+- [about_Execution_Policies][01]
+- [about_Group_Policy_Settings][02]
+- [about_Scripts][03]
+
+<!-- link references -->
+[01]: about_Execution_Policies.md
+[02]: about_Group_Policy_Settings.md
+[03]: about_Scripts.md
diff --git a/reference/7.4/Microsoft.PowerShell.Core/About/about_Signing.md b/reference/7.4/Microsoft.PowerShell.Core/About/about_Signing.md
index ba47b83701c..5a34745dd85 100644
--- a/reference/7.4/Microsoft.PowerShell.Core/About/about_Signing.md
+++ b/reference/7.4/Microsoft.PowerShell.Core/About/about_Signing.md
@@ -1,7 +1,7 @@
 ---
 description: Explains how to sign scripts so that they comply with the PowerShell execution policies.
 Locale: en-US
-ms.date: 06/05/2023
+ms.date: 10/23/2023
 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_signing?view=powershell-7.4&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: about Signing
@@ -142,9 +142,8 @@ topic.
 ## Create a self-signed certificate
 
 To create a self-signed certificate, use the [New-SelfSignedCertificate][04]
-cmdlet in the PKI module. This module is introduced in PowerShell 3.0 and is
-included in Windows 8 and Windows Server 2012. For more information, see the
-help topic for the `New-SelfSignedCertificate` cmdlet.
+cmdlet in the PKI module. This module is introduced in PowerShell 3.0. For more
+information, see the help topic for the `New-SelfSignedCertificate` cmdlet.
 
 ```powershell
 $params = @{
diff --git a/reference/7.4/Microsoft.PowerShell.Security/New-FileCatalog.md b/reference/7.4/Microsoft.PowerShell.Security/New-FileCatalog.md
index e74aca1db49..a6b2a603516 100644
--- a/reference/7.4/Microsoft.PowerShell.Security/New-FileCatalog.md
+++ b/reference/7.4/Microsoft.PowerShell.Security/New-FileCatalog.md
@@ -2,7 +2,7 @@
 external help file: Microsoft.PowerShell.Security.dll-Help.xml
 Locale: en-US
 Module Name: Microsoft.PowerShell.Security
-ms.date: 12/12/2022
+ms.date: 10/23/2023
 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.security/new-filecatalog?view=powershell-7.4&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: New-FileCatalog
@@ -31,9 +31,7 @@ paths. Users can then distribute the catalog with their files so that users can
 changes have been made to the folders since catalog creation time.
 
 Catalog versions 1 and 2 are supported. Version 1 uses the (deprecated) SHA1 hashing algorithm to
-create file hashes, and version 2 uses SHA256. Catalog version 2 is not supported on Windows Server
-2008 R2 or Windows 7. You should use catalog version 2 on Windows 8, Windows Server 2012, and later
-operating systems.
+create file hashes, and version 2 uses SHA256.
 
 ## EXAMPLES
 
diff --git a/reference/7.4/Microsoft.PowerShell.Security/Set-Acl.md b/reference/7.4/Microsoft.PowerShell.Security/Set-Acl.md
index 5ec592329e5..319f1aaf83a 100644
--- a/reference/7.4/Microsoft.PowerShell.Security/Set-Acl.md
+++ b/reference/7.4/Microsoft.PowerShell.Security/Set-Acl.md
@@ -2,7 +2,7 @@
 external help file: Microsoft.PowerShell.Security.dll-Help.xml
 Locale: en-US
 Module Name: Microsoft.PowerShell.Security
-ms.date: 12/12/2022
+ms.date: 10/23/2023
 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.security/set-acl?view=powershell-7.4&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: Set-Acl
diff --git a/reference/docs-conceptual/developer/installing-the-windows-powershell-sdk.md b/reference/docs-conceptual/developer/installing-the-windows-powershell-sdk.md
index 94d3fbe1562..5c33215bcd9 100644
--- a/reference/docs-conceptual/developer/installing-the-windows-powershell-sdk.md
+++ b/reference/docs-conceptual/developer/installing-the-windows-powershell-sdk.md
@@ -1,6 +1,6 @@
 ---
 description: Installing the Windows PowerShell SDK
-ms.date: 03/30/2020
+ms.date: 10/23/2023
 ms.topic: reference
 title: Installing the Windows PowerShell SDK
 ---
@@ -22,18 +22,6 @@ SDK download site. Windows PowerShell code samples are also available in the
 [powershell-sdk-samples](https://github.com/MicrosoftDocs/powershell-sdk-samples/tree/master/SDK-3.0)
 repository.
 
-## Installing Windows PowerShell 3.0 SDK for Windows 7 and Windows Server 2008 R2
-
-Windows 7 and Windows Server 2008 R2 automatically have PowerShell 2.0 installed. In addition, you
-can install PowerShell 3.0 on these systems. You can also install the Windows 8 SDK on Windows 7 and
-Windows Server 2008 R2 as described above.
-
-## Installing Windows PowerShell 2.0 SDK for Windows 7, Vista, XP, Server 2003, and Server 2008
-
-The Windows PowerShell 2.0 SDK provides the reference assemblies needed to write cmdlets, providers,
-and hosting applications, and it provides C# sample code that can be used as the starting point when
-you begin writing code.
-
 ### Reference assemblies
 
 Reference assemblies are installed in the following location by default: `c:\Program Files\Reference
diff --git a/reference/docs-conceptual/learn/remoting/PS-remoting-second-hop.md b/reference/docs-conceptual/learn/remoting/PS-remoting-second-hop.md
index 46784c6c22a..75e62bc743b 100644
--- a/reference/docs-conceptual/learn/remoting/PS-remoting-second-hop.md
+++ b/reference/docs-conceptual/learn/remoting/PS-remoting-second-hop.md
@@ -1,6 +1,6 @@
 ---
 description: This article explains the various methods for configuring second-hop authentication for PowerShell remoting, including the security implications and recommendations.
-ms.date: 11/16/2022
+ms.date: 10/23/2023
 title: Making the second hop in PowerShell Remoting
 ---
 
@@ -114,8 +114,8 @@ credentials.
 
 Let's look at a PowerShell example that configures resource-based constrained delegation on
 _ServerC_ to allow delegated credentials from a _ServerB_. This example assumes that all servers are
-running Windows Server 2012 or later, and that there is at least one Windows Server 2012 domain
-controller each domain to which any of the servers belong.
+running supported versions of Windows Server, and that there is at least one Windows domain
+controller for each trusted domain.
 
 Before you can configure constrained delegation, you must add the `RSAT-AD-PowerShell` feature to
 install the Active Directory PowerShell module, and then import that module into your session:
diff --git a/reference/docs-conceptual/learn/remoting/WinRMSecurity.md b/reference/docs-conceptual/learn/remoting/WinRMSecurity.md
index d43b1f92bad..b2743ffdea5 100644
--- a/reference/docs-conceptual/learn/remoting/WinRMSecurity.md
+++ b/reference/docs-conceptual/learn/remoting/WinRMSecurity.md
@@ -1,21 +1,21 @@
 ---
 description: This document covers security concerns, recommendations, and best practices when using PowerShell Remoting.
-ms.date: 11/16/2022
+ms.date: 10/23/2023
 title: Security considerations for PowerShell Remoting using WinRM
 ---
 
 # Security Considerations for PowerShell Remoting using WinRM
 
 PowerShell Remoting is the recommended way to manage Windows systems. PowerShell Remoting is enabled
-by default in Windows Server 2012 R2. This document covers security concerns, recommendations, and
-best practices when using PowerShell Remoting.
+by default in Windows Server 2012 R2 and higher. This document covers security concerns,
+recommendations, and best practices when using PowerShell Remoting.
 
 ## What is PowerShell Remoting?
 
-PowerShell Remoting uses [Windows Remote Management (WinRM)][04], which is the Microsoft
-implementation of the [Web Services for Management (WS-Management)][05] protocol, to allow users to
-run PowerShell commands on remote computers. You can find more information about using PowerShell
-Remoting at [Running Remote Commands][08].
+PowerShell Remoting uses [Windows Remote Management (WinRM)][04] to allow users to run PowerShell
+commands on remote computers. WinRM is the Microsoft implementation of the
+[Web Services for Management (WS-Management)][05] protocol. You can find more information about
+using PowerShell Remoting at [Running Remote Commands][08].
 
 PowerShell Remoting isn't the same as using the **ComputerName** parameter of a cmdlet to run it on
 a remote computer, which uses Remote Procedure Call (RPC) as its underlying protocol.
diff --git a/reference/docs-conceptual/learn/remoting/jea/prerequisites.md b/reference/docs-conceptual/learn/remoting/jea/prerequisites.md
index 0153eaf8ac9..187ba0c9330 100644
--- a/reference/docs-conceptual/learn/remoting/jea/prerequisites.md
+++ b/reference/docs-conceptual/learn/remoting/jea/prerequisites.md
@@ -1,6 +1,6 @@
 ---
 description: This article describes the prerequisites that must be satisfied to start using JEA.
-ms.date: 11/16/2022
+ms.date: 10/23/2023
 title: JEA Prerequisites
 ---
 # JEA Prerequisites
@@ -73,7 +73,7 @@ PowerShell Remoting provides the foundation on which JEA is built. It's necessar
 PowerShell Remoting is enabled and properly secured before you can use JEA. For more information,
 see [WinRM Security][01].
 
-PowerShell Remoting is enabled by default on Windows Server 2012, 2012 R2, and 2016. You can enable
+PowerShell Remoting is enabled by default on Windows Server 2012 and higher. You can enable
 PowerShell Remoting by running the following command in an elevated PowerShell window.
 
 ```powershell
diff --git a/reference/docs-conceptual/whats-new/Migrating-from-Windows-PowerShell-51-to-PowerShell-7.md b/reference/docs-conceptual/whats-new/Migrating-from-Windows-PowerShell-51-to-PowerShell-7.md
index eaccb6b411b..5b1929e9a00 100644
--- a/reference/docs-conceptual/whats-new/Migrating-from-Windows-PowerShell-51-to-PowerShell-7.md
+++ b/reference/docs-conceptual/whats-new/Migrating-from-Windows-PowerShell-51-to-PowerShell-7.md
@@ -1,6 +1,6 @@
 ---
 description: Update from PowerShell 5.1 to PowerShell 7 for your Windows platforms.
-ms.date: 03/01/2023
+ms.date: 10/23/2023
 title: Migrating from Windows PowerShell 5.1 to PowerShell 7
 ---
 
@@ -22,8 +22,8 @@ editions before deployment. Migration is simple, quick, and safe.
 
 PowerShell 7 is supported on the following Windows operating systems:
 
-- Windows 8.1, 10, and 11
-- Windows Server 2012, 2012 R2, 2016, 2019, and 2022
+- Windows 10, and 11
+- Windows Server 2016, 2019, and 2022
 
 PowerShell 7 also runs on macOS and several Linux distributions. For a list of supported operating
 systems and information about the support lifecycle, see the [PowerShell Support Lifecycle][04].
diff --git a/reference/docs-conceptual/windows-powershell/Starting-Windows-PowerShell.md b/reference/docs-conceptual/windows-powershell/Starting-Windows-PowerShell.md
index 151b46c4405..383a36f6dcd 100644
--- a/reference/docs-conceptual/windows-powershell/Starting-Windows-PowerShell.md
+++ b/reference/docs-conceptual/windows-powershell/Starting-Windows-PowerShell.md
@@ -1,18 +1,15 @@
 ---
 description: This article explains the ways of starting various versions of PowerShell.
-ms.date: 05/04/2023
+ms.date: 10/23/2023
 title: Starting Windows PowerShell
 ---
 
 # Starting Windows PowerShell
 
-Windows PowerShell is a scripting engine `.DLL` that's embedded into multiple hosts. The most common
-hosts you'll start are the interactive command-line `powershell.exe` and the Interactive Scripting
+Windows PowerShell is a scripting engine that's embedded into multiple hosts. The most common hosts
+you'll start are the interactive command-line `powershell.exe` and the Interactive Scripting
 Environment `powershell_ise.exe`.
 
-To start Windows PowerShell on Windows Server 2012 R2, Windows 8.1, Windows Server 2012, and Windows
-8, see [Common Management Tasks and Navigation in Windows][08].
-
 ## PowerShell has renamed binary
 
 PowerShell version 6 and higher uses .NET Core. Supported versions are available on Windows, macOS,
@@ -82,54 +79,17 @@ PowerShell, type: `PowerShell_ISE`. In Windows PowerShell, you can use the alias
 Click **Start**, type **ISE**, right-click **Windows PowerShell ISE**, and then click **Run as
 administrator**.
 
-## How to Enable Windows PowerShell ISE on Earlier Releases of Windows
-
-In Windows PowerShell 4.0 and Windows PowerShell 3.0, Windows PowerShell ISE is enabled by default
-on all versions of Windows. If it isn't already enabled, Windows Management Framework 4.0 or Windows
-Management Framework 3.0 enables it.
-
-In Windows PowerShell 2.0, Windows PowerShell ISE is enabled by default on Windows 7. However, on
-Windows Server 2008 R2 and Windows Server 2008, it's an optional feature.
-
-To enable Windows PowerShell ISE in Windows PowerShell 2.0 on Windows Server 2008 R2 or Windows
-Server 2008, use the following procedure.
-
-### To enable Windows PowerShell Integrated Scripting Environment (ISE)
-
-1. Start Server Manager.
-1. Click **Features** and then click **Add Features**.
-1. In Select Features, click Windows PowerShell Integrated Scripting Environment (ISE).
-
 ## Starting the 32-Bit Version of Windows PowerShell
 
-When you install Windows PowerShell on a 64-bit computer, **Windows PowerShell (x86)**, a 32-bit
-version of Windows PowerShell is installed in addition to the 64-bit version. When you run Windows
-PowerShell, the 64-bit version runs by default.
+When using a 64-bit computer, **Windows PowerShell (x86)**, a 32-bit version of Windows PowerShell
+is installed in addition to the 64-bit version. When you run Windows PowerShell, the 64-bit version
+runs by default.
 
 However, you might occasionally need to run **Windows PowerShell (x86)**, such as when you're using
 a module that requires the 32-bit version or when you're connecting remotely to a 32-bit computer.
 
 To start a 32-bit version of Windows PowerShell, use any of the following procedures.
 
-### In Windows Server 2012 R2
-
-- On the **Start** screen, type **Windows PowerShell (x86)**. Click the **Windows PowerShell x86**
-  tile.
-- In **Server Manager**, from the **Tools** menu, select **Windows PowerShell (x86)**.
-- On the desktop, move the cursor to the upper right corner, click **Search**, type **PowerShell
-  x86** and then click **Windows PowerShell (x86)**.
-- Via command line, enter: `%SystemRoot%\SysWOW64\WindowsPowerShell\v1.0\powershell.exe`
-
-### In Windows 8.1
-
-- On the **Start** screen, type **Windows PowerShell (x86)**. Click the **Windows PowerShell x86**
-  tile.
-- If you're running [Remote Server Administration Tools][09] for Windows 8.1, you can also open
-  Windows PowerShell x86 from the **Server ManagerTools** menu. Select **Windows PowerShell (x86)**.
-- On the desktop, move the cursor to the upper right corner, click **Search**, type **PowerShell
-  x86** and then click **Windows PowerShell (x86)**.
-- Via command line, enter: `%SystemRoot%\SysWOW64\WindowsPowerShell\v1.0\powershell.exe`
-
 <!-- link references -->
 [01]: ../how-to-use-docs.md
 [02]: /powershell/module/
@@ -138,5 +98,3 @@ To start a 32-bit version of Windows PowerShell, use any of the following proced
 [05]: /powershell/scripting/install/installing-powershell-on-linux
 [06]: /powershell/scripting/install/installing-powershell-on-macos
 [07]: /powershell/scripting/install/installing-powershell-on-windows
-[08]: /previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831491(v=ws.11)
-[09]: https://go.microsoft.com/fwlink/?LinkID=304145
diff --git a/reference/docs-conceptual/windows-powershell/install/Windows-PowerShell-System-Requirements.md b/reference/docs-conceptual/windows-powershell/install/Windows-PowerShell-System-Requirements.md
index da4aee933ac..17bafbb835e 100644
--- a/reference/docs-conceptual/windows-powershell/install/Windows-PowerShell-System-Requirements.md
+++ b/reference/docs-conceptual/windows-powershell/install/Windows-PowerShell-System-Requirements.md
@@ -1,6 +1,6 @@
 ---
 description: This article lists the system requirements for Windows PowerShell 3.0, Windows PowerShell 4.0, Windows PowerShell 5.0, and Windows PowerShell 5.1.
-ms.date: 10/25/2022
+ms.date: 10/23/2023
 title: Windows PowerShell System Requirements
 ---
 
diff --git a/reference/docs-conceptual/windows-powershell/wmf/overview.md b/reference/docs-conceptual/windows-powershell/wmf/overview.md
index 9460e746813..7218560ca62 100644
--- a/reference/docs-conceptual/windows-powershell/wmf/overview.md
+++ b/reference/docs-conceptual/windows-powershell/wmf/overview.md
@@ -1,6 +1,6 @@
 ---
 description: WMF is a prerequisite for Windows PowerShell. This articles shows the history of WMF versions and provides information about how to find and install WMF.
-ms.date: 09/11/2023
+ms.date: 10/23/2023
 title: Windows Management Framework (WMF)
 ---
 
@@ -32,23 +32,23 @@ to the links below to review the release notes:
 
 ## WMF availability across Windows operating systems
 
-|         OS Version         |     End of Support     |      WMF 5.1      |            WMF 5.0             | WMF 4.0  | WMF 3.0  | WMF 2.0  |
-| -------------------------- | ---------------------- | ----------------- | ------------------------------ | -------- | -------- | -------- |
-| Windows Server 2022        | [2031-10-14][04]       | Included          |                                |          |          |          |
-| Windows Server 2019        | [2029-01-09][04]       | Included          |                                |          |          |          |
-| Windows Server 2016        | [2027-01-11][04]       | Included          |                                |          |          |          |
-| Windows 11                 | [2025-10-14][03]       | Included          |                                |          |          |          |
-| Windows 10                 | [2025-10-14][03]       | Included in 1607+ | Included<br>(replaced in 1607) |          |          |          |
-| Windows Server 2012 R2     | [2023-10-10][02]       | [Yes][05]         | Yes                            | Included |          |          |
-| Windows 8.1                | [_Out of support_][02] | [Yes][05]         | Yes                            | Included |          |          |
-| Windows Server 2012        | [2023-10-10][02]       | [Yes][05]         | Yes                            | Yes      | Included |          |
-| Windows 8                  | [_Out of support_][01] |                   |                                |          | Included |          |
-| Windows Server 2008 R2 SP1 | [_Out of support_][01] | [Yes][05]         | Yes                            | Yes      | Yes      | Included |
-| Windows 7 SP1              | [_Out of support_][01] | [Yes][05]         | Yes                            | Yes      | Yes      | Included |
-| Windows Server 2008 SP2    | [_Out of support_][01] |                   |                                |          | Yes      | Yes      |
-| Windows Vista              | [_Out of support_][01] |                   |                                |          |          | Yes      |
-| Windows Server 2003        | [_Out of support_][01] |                   |                                |          |          | Yes      |
-| Windows XP                 | [_Out of support_][01] |                   |                                |          | Yes      | Yes      |
+|         OS Version         |     End of Support     |      WMF 5.1      | WMF 5.0  | WMF 4.0  | WMF 3.0  | WMF 2.0  |
+| -------------------------- | ---------------------- | ----------------- | -------- | -------- | -------- | -------- |
+| Windows Server 2022        | [2031-10-14][04]       | Included          |          |          |          |          |
+| Windows Server 2019        | [2029-01-09][04]       | Included          |          |          |          |          |
+| Windows Server 2016        | [2027-01-11][04]       | Included          |          |          |          |          |
+| Windows 11                 | [2025-10-14][03]       | Included          |          |          |          |          |
+| Windows 10                 | [2025-10-14][03]       | Included in 1607+ | Included |          |          |          |
+| Windows Server 2012 R2     | [_Out of support_][02] | [Yes][05]         | Yes      | Included |          |          |
+| Windows 8.1                | [_Out of support_][02] | [Yes][05]         | Yes      | Included |          |          |
+| Windows Server 2012        | [_Out of support_][02] | [Yes][05]         | Yes      | Yes      | Included |          |
+| Windows 8                  | [_Out of support_][01] |                   |          |          | Included |          |
+| Windows Server 2008 R2 SP1 | [_Out of support_][01] | [Yes][05]         | Yes      | Yes      | Yes      | Included |
+| Windows 7 SP1              | [_Out of support_][01] | [Yes][05]         | Yes      | Yes      | Yes      | Included |
+| Windows Server 2008 SP2    | [_Out of support_][01] |                   |          |          | Yes      | Yes      |
+| Windows Vista              | [_Out of support_][01] |                   |          |          |          | Yes      |
+| Windows Server 2003        | [_Out of support_][01] |                   |          |          |          | Yes      |
+| Windows XP                 | [_Out of support_][01] |                   |          |          | Yes      | Yes      |
 
 - **Included**: The features of the specified version of WMF were shipped in the indicated version
   of Windows client or Windows Server.
diff --git a/reference/includes/windows-support.md b/reference/includes/windows-support.md
index 069bfca26fe..dc8a4101117 100644
--- a/reference/includes/windows-support.md
+++ b/reference/includes/windows-support.md
@@ -1,7 +1,7 @@
 ---
 author: sdwheeler
 ms.author: sewhee
-ms.date: 01/09/2023
+ms.date: 10/23/2023
 ms.prod: powershell
 ms.topic: include
 ---
@@ -24,14 +24,12 @@ on. These versions are supported until either the version of
 [3]: ../media/shared/cross-mark-274c.svg
 [4]: ../media/shared/large-yellow-circle-1f7e1.svg
 
-|                         Windows                         | 7.2 (LTS-current) |       7.3       |  7.4 (preview)  |
-| ------------------------------------------------------- | :---------------: | :-------------: | :-------------: |
-| ![Supported][1] Windows Server 2016, 2019, or 2022      |  ![Supported][1]  | ![Supported][1] | ![Supported][1] |
-| ![Supported][1] Windows Server 2012 R2                  |  ![Supported][1]  | ![Supported][1] | ![Supported][1] |
-| ![Supported][1] Windows Server Core (2012 R2 or higher) |  ![Supported][1]  | ![Supported][1] | ![Supported][1] |
-| ![Supported][1] Windows Server Nano (1809 or higher)    |  ![Supported][1]  | ![Supported][1] | ![Supported][1] |
-| ![Supported][1] Windows 11                              |  ![Supported][1]  | ![Supported][1] | ![Supported][1] |
-| ![Supported][1] Windows 10 1607+                        |  ![Supported][1]  | ![Supported][1] | ![Supported][1] |
+|                       Windows                        | 7.2 (LTS-current) |       7.3       |  7.4 (preview)  |
+| ---------------------------------------------------- | :---------------: | :-------------: | :-------------: |
+| ![Supported][1] Windows Server 2016, 2019, or 2022   |  ![Supported][1]  | ![Supported][1] | ![Supported][1] |
+| ![Supported][1] Windows Server Nano (1809 or higher) |  ![Supported][1]  | ![Supported][1] | ![Supported][1] |
+| ![Supported][1] Windows 11                           |  ![Supported][1]  | ![Supported][1] | ![Supported][1] |
+| ![Supported][1] Windows 10 1607+                     |  ![Supported][1]  | ![Supported][1] | ![Supported][1] |
 
 > [!NOTE]
 > Support for a specific version of Windows is determined by the Microsoft Support Lifecycle
@@ -42,12 +40,13 @@ on. These versions are supported until either the version of
 
 PowerShell is supported on Windows for the following processor architectures.
 
-|           Windows            | 7.2 (LTS-current) |       7.3       |  7.4 (preview)  |
-| ---------------------------- | :---------------: | :-------------: | :-------------: |
-| Nano Server Version 1803+    |        x64        |       x64       |       x64       |
-| Windows Server 2012 R2+      |     x64, x86      |    x64, x86     |    x64, x86     |
-| Windows Server Core 2012 R2+ |     x64, x86      |    x64, x86     |    x64, x86     |
-| Windows 10 or 11 Client      |  x64, x86, Arm64  | x64, x86, Arm64 | x64, x86, Arm64 |
+|          Windows          | 7.2 (LTS-current) |       7.3       |  7.4 (preview)  |
+| ------------------------- | :---------------: | :-------------: | :-------------: |
+| Windows Server 2016+      |     x64, x86      |    x64, x86     |    x64, x86     |
+| Windows Server Core 2016+ |     x64, x86      |    x64, x86     |    x64, x86     |
+| Nano Server Version 1803+ |        x64        |       x64       |       x64       |
+| Windows 11 Client         |    x64, Arm64     |   x64, Arm64    |   x64, Arm64    |
+| Windows 10 Client         |  x64, x86, Arm64  | x64, x86, Arm64 | x64, x86, Arm64 |
 
 [lifecycle]: /powershell/scripting/install/powershell-support-lifecycle
 [eol-windows]: /lifecycle/products/?terms=Windows%20Server&products=windows