fix(Infrastructure integrations): Broken link

Fixed a broken link and made a few other minor copyedits. Fixes #4217

src/content/docs/infrastructure/install-infrastructure-agent/windows-installation/zip-manual-install-infrastructure-agent-windows.mdx

@@ -10,9 +10,9 @@ redirects:
   - /docs/infrastructure/install-configure-infrastructure/windows-installation/manual-install-infrastructure-windows
 ---
 
-Our custom installation process for the infrastructure agent for Windows allows you to tailor all aspects of the installation, and place files and folders wherever you want on your filesystem.
+Our custom installation process for the infrastructure agent for Windows allows you to tailor all aspects of the installation. You can place files and folders wherever you want on your filesystem.
 
-This method gives you **full control** of the installation: **you are responsible** for placing the files in the correct folders, providing the correct configuration values, and ensuring the agent has all the right permissions.
+This method gives you **full control** of the installation. You are responsible for placing the files in the correct folders, providing the correct configuration values, and ensuring the agent has all the right permissions.
 
 Before installation, check the [compatibility and requirements](/docs/infrastructure/install-infrastructure-agent/get-started/requirements-infrastructure-agent).
 
@@ -35,7 +35,7 @@ To install the agent:
 * [Configure the log file](#log-file).
 
 <Callout variant="important">
-  As of [version 1.4.0](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-140), the infrastructure agent package includes the additional `newrelic-infra-ctl` binary, which is used to help troubleshoot a running agent. Although this binary is not required to execute the agent, we recommend to add it in your path. [See our docs](/docs/infrastructure/install-configure-manage-infrastructure/manage-your-agent/troubleshoot-running-agent) for more information.
+  As of [version 1.4.0](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-140), the infrastructure agent package includes the additional `newrelic-infra-ctl` binary, which is used to help troubleshoot a running agent. Although this binary is not required to execute the agent, we recommend to add it in your path. For more information, see our documentation about [troubleshooting a running infrastructure agent](/docs/infrastructure/install-configure-manage-infrastructure/manage-your-agent/troubleshoot-running-agent).
 </Callout>
 
 ## Install the service script [#install-service-script]
@@ -48,7 +48,9 @@ C:\Program Files\New Relic\newrelic-infra\installer.ps1
 
 ## Configuration file [#change-config-file]
 
-The Infrastructure agent depends on a configuration file, usually named `newrelic-infra.yml`, placed in the same folder with the agent, to configure the agent's behavior. You can create a new config file based on [config file template](/docs/infrastructure/new-relic-infrastructure/configuration/infrastructure-config-file-template-newrelic-infrayml). For more information, see how to [configure the agent](/docs/infrastructure/new-relic-infrastructure/configuration/configure-infrastructure-agent).
+The infrastructure agent depends on a configuration file, usually named `newrelic-infra.yml`, to configure the agent's behavior. This file is placed in the same folder with the agent.
+
+You can create a new config file based on the [config file template](/docs/infrastructure/new-relic-infrastructure/configuration/infrastructure-config-file-template-newrelic-infrayml). For more information, see how to [configure the agent](/docs/infrastructure/new-relic-infrastructure/configuration/configure-infrastructure-agent).
 
 ### Changing the config file's location
 
@@ -67,7 +69,9 @@ To change the location of the configuration file:
 
 ## Configure the plugin directory [#configure-plugin]
 
-The Infrastructure agent allows you to install [integrations](/docs/integrations) that monitor and report data from popular services such as Kubernetes, AWS, MySQL, Redis, Kafka, etc. Each integration has its own configuration file, named by default `integration-name-config.yml`, placed in the predefined location `C:\Program Files\New Relic\newrelic-infra\integrations.d`. On initialization, the agent loads the config file.
+The infrastructure agent allows you to install [integrations](/docs/integrations) that monitor and report data from popular services such as Kubernetes, AWS, MySQL, Redis, Kafka, etc. Each integration has its own configuration file, named `integration-name-config.yml` by default.
+
+This config file is placed in the predefined location `C:\Program Files\New Relic\newrelic-infra\integrations.d`. On initialization, the agent loads the config file.
 
 To overwrite the predefined location of the integration configuration file, use one of the following methods:
 
@@ -81,11 +85,11 @@ The agent requires its own defined directory to run the installed [integrations]
 
 The agent directory has the following structure and content:
 
-* `LICENSE`: Text file containing the New Relic Infrastructure agent license.
+* `LICENSE`: Text file containing the New Relic infrastructure agent license.
 * `custom-integrations`: Directory that stores the installed the [custom integrations](/docs/integrations/integrations-sdk/getting-started/introduction-infrastructure-integrations-sdk).
-* `newrelic-integrations`: Directory that stores the [New Relic official integrations](/docs/infrastructure/integrations/types-integrations).
+* `newrelic-integrations`: Directory that stores the [New Relic official integrations](/docs/i/integrations).
 
-Additionally, the agent uses a different folder, `app_data_dir`, to store data. By default it points to `C:\ProgramData\New Relic\newrelic-infra\`.
+The agent also uses a different folder, `app_data_dir`, to store data. By default it points to `C:\ProgramData\New Relic\newrelic-infra\`.
 
 To overwrite the predefined location of the agent directory, use one of the following methods:
 
@@ -107,7 +111,7 @@ To overwrite the predefined location of the log file, use one of the following m
 
 You may also want to:
 
-* [Add custom attributes](/docs/Infrastructure-configure-your-agent#conf-custom_attributes) to annotate your Infrastructure data.
-* [Connect your AWS account](/docs/infrastructure-amazon-aws-ec2-integration#connect) if your servers are hosted on Amazon EC2.
-* Add other [New Relic Infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) to collect data from external services.
-* Manually [start, stop, restart, or check the agent status](/docs/infrastructure-start-stop-restart-check-agent-status#linux).
+* [Add custom attributes](/docs/infrastructure/install-infrastructure-agent/configuration/infrastructure-agent-configuration-settings/#custom-attributes) to annotate your infrastructure data.
+* [Connect your AWS account](/docs/integrations/amazon-integrations/get-started/connect-aws-new-relic-infrastructure-monitoring/) if your servers are hosted on Amazon EC2.
+* Add other [New Relic infrastructure integrations](/docs/integrations/infrastructure-integrations/get-started/introduction-infrastructure-integrations/) to collect data from external services.
+* Manually [start, stop, restart, or check the agent status](/docs/infrastructure/install-infrastructure-agent/manage-your-agent/start-stop-restart-infrastructure-agent/#windows).