More Fixes (#556)

Docs/index.md

@@ -3,7 +3,7 @@
 Enterprise Azure Policy as Code (EPAC for short) is a number of PowerShell scripts which can be used in CI/CD based system or a semi-automated use to deploy Policies, Policy Sets, Policy Assignments, Policy Exemptions and Role Assignments. It also contains operational scripts to simplify operational tasks.
 
 > [!CAUTION]
-> v10.0.0 has breaking changes. Please review the [Changes](changes.md) document.
+> v10.0.0 has breaking changes. Please review the [Changes](start-changes.md) document.
 
 > [!IMPORTANT]
 > Starting with v8.0.0, Enterprise Policy as Code (EPAC) is tracking the usage using [Customer Usage Attribution](https://learn.microsoft.com/en-us/partner-center/marketplace/azure-partner-customer-usage-attribution). In accordance with Microsoft's privacy policies, you have the right to **opt-out** of this tracking. Please review [Telemetry below](#telemetry-tracking-using-customer-usage-attribution-pid) and [Microsoft Privacy](https://privacy.microsoft.com/en-US/) for more information.

Docs/operational-scripts.md

@@ -20,7 +20,7 @@ This script executes all remediation tasks in a Policy as Code environment speci
 
 ## Policy Resources Exports
 
-- `Export-AzPolicyResources` exports Azure Policy resources in EPAC. It also generates documentation for the exported resources (can be suppressed with `-SuppressDocumentation`). See usage documentation in [Extract existing Policy Resources](epac-extracting-policy-resources.md).
+- `Export-AzPolicyResources` exports Azure Policy resources in EPAC. It also generates documentation for the exported resources (can be suppressed with `-SuppressDocumentation`). See usage documentation in [Extract existing Policy Resources](start-extracting-policy-resources.md).
 - `Get-AzExemptions` retrieves Policy Exemptions from an EPAC environment and saves them to files.
 - `Get-AzPolicyAliasOutputCSV` exports Policy Aliases to CSV format.
 

Docs/policy-assignments.md

@@ -170,7 +170,7 @@ This example generates two assignments at the "prod" leaf per scope:
 
 `scope` is required exactly once in each tree branch. Excluded scopes (`notScope`) are cumulative from `global-settings.json` and the entire tree branch; however, once a scope is defined `notScope` may not be defined at any child node.
 
-Both `scope` and `notScope` are specific to an [EPAC Environment using the pacSelector name](epac-implementing.md#epac-concepts-and-environments), e.g., `epac-dev` and `tenant`.
+Both `scope` and `notScope` are specific to an [EPAC Environment using the pacSelector name](start-implementing.md#epac-concepts-and-environments), e.g., `epac-dev` and `tenant`.
 
 ```json
 "scope": {

Docs/policy-exemptions.md

@@ -4,7 +4,7 @@
 
 Exemptions can be defined as JSON or CSV files (we recommend that you use CSV files). The names of the definition files don't matter. If multiple files exists in a folder, the lists from all the files are added together.
 
-The pacEnvironment (see global-settings.jsonc) is represented with a folder structure under the folder policyExemptions, such as epac-dev, tenant, ... A missing folder indicates that the pacEnvironment's Exemptions are not managed by this solution. To extract existing exemptions, the operations script Get-AzExemptions.ps1 can be used to generate JSON and CSV files. The output may be used to start the Exemption definitions. This same output is also created when [Extract existing Policy Resources from an Environment](epac-extracting-policy-resources.md).
+The pacEnvironment (see global-settings.jsonc) is represented with a folder structure under the folder policyExemptions, such as epac-dev, tenant, ... A missing folder indicates that the pacEnvironment's Exemptions are not managed by this solution. To extract existing exemptions, the operations script Get-AzExemptions.ps1 can be used to generate JSON and CSV files. The output may be used to start the Exemption definitions. This same output is also created when [Extract existing Policy Resources from an Environment](start-extracting-policy-resources.md).
 
 A typical folder structure might look like this:
 

Docs/settings-global-setting-file.md

@@ -58,7 +58,7 @@ To utilize the schema add a ```$schema``` tag to the JSON file.
 
 ## Opt out of telemetry data collection `telemetryOptOut`
 
-Starting with v8.0.0, Enterprise Policy as Code (EPAC) is tracking the usage using Customer Usage Attribution (PID). See [Usage Tracking](epac-overview.md#telemetry-tracking-using-customer-usage-attribution-pid) for more information on opt out. Default is false.
+Starting with v8.0.0, Enterprise Policy as Code (EPAC) is tracking the usage using Customer Usage Attribution (PID). See [Usage Tracking](index.md#telemetry-tracking-using-customer-usage-attribution-pid) for more information on opt out. Default is false.
 
 ```json
 "telemetryOptOut": true,

Docs/start-implementing.md

@@ -15,7 +15,7 @@ The following steps are required to implement Enterprise Policy as Code (EPAC) i
 5. Create your [`Definitions` folder and subfolders](#create-the-definitions-folder).
 6. Populate `global-settings.jsonc` with your [environment settings](settings-global-setting-file.md) and [desired state strategy](settings-dfc-assignments.md).
 7. Populate your Definitions folder with Policy resources.
-    - [Option A:] [Extract existing Policy resources](epac-extracting-policy-resources.md) from your Azure environment.
+    - [Option A:] [Extract existing Policy resources](start-extracting-policy-resources.md) from your Azure environment.
     - [Option B:] [Integrate Azure Landing Zones (ALZ)](integrating-with-alz.md).
     - [Option C:] Utilize the [hydration kit](operational-scripts-hydration-kit.md) and `StarterKit` content.
     - [Optional] Create custom [Policy definitions](policy-definitions.md).