Apply suggestions from code review

Co-Authored-By: Ilya <[email protected]>

Author: TravisEz13

1-Draft/RFCXXXX-Policy.md

@@ -12,7 +12,7 @@ Comments Due: 6/30/2019
 
 ## Motivation
 
-Consumers, developers, and enterprise system administrators should be able to flexibly and reliable way to configure PowerShell 7.
+Consumers, developers, and enterprise system administrators should be able to flexibly and reliable configure PowerShell 7.
 
 ## Acknowledgement
 
@@ -43,11 +43,11 @@ PowerShell 7 has hard-coded defaults for all configuration options.
 
 The default values must be `secure-by-default`.
 
-For release versions hard-coded defaults must be the same as ones in re-installed configuration files. For preview versions they may vary (ex., enable experimental features and so on).
+For release versions hard-coded defaults must be the same as ones in pre-installed configuration files. For preview versions they may vary (ex., enable experimental features and so on).
 
 System configuration includes security sensitive setting,
 and failing to read those setting could result in an insecure system.
-So, if during startup, PowerShell 7 cannot read system configuration files,
+So, if during startup, PowerShell 7 cannot read files read from the Computer-Wide scope,
 it fails to startup.
 
 If during startup PowerShell 7 cannot read user configuration files it uses _hardcoded_ defaults.
@@ -59,13 +59,13 @@ If during operation PowerShell 7 cannot read configuration files it continue to
 `PowerShell 7` settings are grouped into `Policy settings` and `Regular settings`.
 Regular settings are normal configuration settings.
 Regular settings can be treated as default and recommended values.
-Policy settings is high priority and overlap regular settings.
-Policy settings are used by administrators to centrally manage applications.
+Policy settings is high precedence.
+See [Precedence for Policy settings in descending order](#precedence-for-policy-settings-in-descending-order).
+Policy settings are used by administrators to centrally manage PowerShell and  hosted applications.
 
 | Location     | Policy settings                                           | Regular settings                                           |
 |--------------|-----------------------------------------------------------|------------------------------------------------------------|
 | File section | "PowerShell": { "PolicySettings": {...} }                 | "PowerShell": { "RegularSettings": {...} }                 |
-| File section | "OtherPowerShellApplication": { "PolicySettings": {...} } | "OtherPowerShellApplication": { "RegularSettings": {...} } |
 | Registry key | Software\Policies\PowerShellCore                          | Software\PowerShellCore                                    |
 
 ### Policy settings Setting Fall-Back
@@ -90,11 +90,11 @@ Because a configuration setting can be in several schemes, the setting wins acco
 | Scheme                      | Windows                                              | Unix                                                 |
 |-----------------------------|------------------------------------------------------|------------------------------------------------------|
 | GPO -> Computer Policy      | HKLM\Software\Policies\PowerShellCore                | /etc/powershell/powershell.config.json                         |
-| GPO -> User Policy          | HKCU\Software\Policies\PowerShellCore                | See `Comment A` below                                |
+| GPO -> User Policy          | HKCU\Software\Policies\PowerShellCore                | See [`Comment A`](#comment-a) below                                |
 | File -> Computer-Wide       | %ProgramFiles%/PowerShell/powershell.config.json     | /etc/powershell/powershell.config.json     |
 | File -> Application-Startup | pwsh -settingsfile `somepath/powershell.config.json` | pwsh -settingsfile `somepath/powershell.config.json` |
 | File -> User-Wide           | %APPDATA%/powershell.config.json                     | %XDG_CONFIG_HOME%/powershell.config.json             |
-| File -> Application-Wide    | $apphome/powershell.config.json                      | $apphome/powershell.config.json                      |
+| File -> Application-Wide    | $PSHome/powershell.config.json                      | $PSHome/powershell.config.json                      |
 
 Defaults:
 
@@ -207,6 +207,13 @@ I filed [#9632](https://github.com/PowerShell/PowerShell/issues/9632) on Updatab
 
 ### Automatically resolve Windows PowerShell policy conflicts
 
+#### Motivation
+
+This is a description of the alternative to [Policy settings Setting Fall-Back](#policy-settings-setting-fall-back).
+The main purpose of describing the alternative is to describe why it should not be pursued.
+
+#### Description
+
 We could attempt to resolve policy conflicts between PowerShell 7 policy and Windows PowerShell policy.
 This would make the `Precedence for Policy settings` not just a simple list but a complex set of rules that would not be easily understood.  See [this conversation](https://github.com/PowerShell/PowerShell/issues/9309?#issuecomment-480643922).