Delete branching logic and create simple procedural step doc

src/content/docs/infrastructure/host-integrations/host-integrations-list/windows-services-integration.mdx

@@ -14,19 +14,16 @@ import infrastructureWindowsServices from 'images/infrastructure_diagram_windows
 
 New Relic's Windows services integration collects data about the services running on your Microsoft Windows hosts and sends it to our platform. You can check the state and start mode of each service, find out which hosts are running a service, set up <InlinePopover type="alerts" /> for services, and more.
 
-Our integration is bundled with the [Windows infrastructure agent](/docs/infrastructure/install-infrastructure-agent/windows-installation/install-infrastructure-monitoring-agent-windows). If you're monitoring Windows hosts on New Relic, you only need to enable the integration to get Windows services data into our platform.
-
-## Why it matters [#value]
-
-[Microsoft Windows services](https://docs.microsoft.com/en-us/dotnet/framework/windows-services/introduction-to-windows-service-applications) are the Windows equivalent of daemons in Unix and Linux: long-running executables that can be started, stopped, paused, and restarted without a graphical interface. Knowing which services are enabled, or their state or health, is essential when monitoring Windows infrastructure.
-
 With our Windows services integration you can:
 
 * Check all your Windows services, their state (running, stopped, etc.), start mode (auto, manual, etc.), and other service [metadata](#metadata).
 * See which hosts are running specific Windows services.
 * [Set alerts](#set-alerts) based on any Windows services that you are monitoring using New Relic.
 * Install the [Windows Services Quickstart](https://newrelic.com/instant-observability/winservices) or create your own <InlinePopover type="dashboards" /> to track your Windows services.
 
+Our integration is bundled with the [Windows infrastructure agent](/docs/infrastructure/install-infrastructure-agent/windows-installation/install-infrastructure-monitoring-agent-windows). If you're monitoring Windows hosts on New Relic, you only need to enable the integration to get Windows services data into our platform.
+
+
 <img
   title="New Relic - Windows services integration - Metric data"
   alt="New Relic - Windows services integration - Metric data"
@@ -39,13 +36,21 @@ With our Windows services integration you can:
 
 ## Compatibility and requirements [#requirements]
 
-Our integration is compatible with all [Windows versions supported](/docs/infrastructure/install-infrastructure-agent/get-started/requirements-infrastructure-agent) by the New Relic agent.
+Our integration is compatible with all [Windows versions supported](/docs/infrastructure/install-infrastructure-agent/get-started/requirements-infrastructure-agent) by the New Relic infrastructure agent.
 
 You must have <DoNotTranslate>**version 1.12.1 or higher**</DoNotTranslate> for our [infrastructure monitoring agent](/docs/infrastructure/install-infrastructure-agent/windows-installation/install-infrastructure-monitoring-agent-windows) installed on a supported host. The x86 Windows versions are not yet supported.
 
-## Install and activate [#install]
+<Steps>
+    <Step>
+
+## Install the infrastructure agent [#infra-install]
 
-To install the Windows services integration:
+To use the Windows services integration, you need to first [install the infrastructure agent](/docs/infrastructure/install-infrastructure-agent/get-started/install-infrastructure-agent-new-relic/) on the same host. All our on-host integrations require the infrastructure agent, which helps expose and report metrics to New Relic.        
+    </Step>
+    <Step>
+## Configure the Windows services integration [#configure]
+
+To activate and configure the Windows services integration:
 
 1. Change the directory to the integrations folder:
 
@@ -57,31 +62,11 @@ To install the Windows services integration:
    ```shell
    copy winservices-config.yml.sample winservices-config.yml
    ```
-3. Edit the `winservices-config.yml` file as described in the [configuration settings](#config) and save it.
-
-### Update your integration [#update]
-
-The Windows services integration is bundled with the infrastructure monitoring agent. To update the integration, [update the agent](/docs/infrastructure/install-infrastructure-agent/update-or-uninstall/update-infrastructure-agent/) to the latest version.
-
-## Configure the integration [#config]
-
-To enable the integration, edit and save the `winservices-config.yml`:
-
-* Uncomment `exporter_bind_address:` and `exporter_bind_port:`
-* Add the name of the services you want to monitor to `include_matching_entities:`
-
-By default, no service is included. To include and filter services, you must edit `include_matching_entities:`.
+3. Edit the `winservices-config.yml` file. By default, no service is included. To include and filter services, you must edit `include_matching_entities:`.
 
-Also, the configuration option [`inventory_source`](/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/specifications/host-integrations-standard-configuration-format) is not compatible with the integration.
+  Here's an example of the Windows services integration configuration with both a regex pattern matching all services named `win32.*` and a direct match for the `newrelic-infra` service:
 
-Here's an example of the Windows services integration configuration with both a regex pattern matching all services named `win32.*` and a direct match for the `newrelic-infra` service:
-
-<CollapserGroup>
-  <Collapser
-    id="example"
-    title="winservices-config.yml"
-  >
-    ```yml
+  ```yml
     integrations:
       - name: nri-winservices
         config:
@@ -95,9 +80,34 @@ Here's an example of the Windows services integration configuration with both a
         timeout: 60s
     ```
 
-    For more information, see our documentation about the [general structure of on-host integration configurations](/docs/integrations/integrations-sdk/file-specifications/host-integration-configuration-overview).
-  </Collapser>
-</CollapserGroup>
+For more information, see our documentation about the [general structure of on-host integration configurations](/docs/integrations/integrations-sdk/file-specifications/host-integration-configuration-overview).
+
+    </Step>
+    <Step>
+## Restart the New Relic infrastructure agent
+
+Restart your infrastructure agent:
+
+```shell
+sudo systemctl restart newrelic-infra.service
+```
+
+In a couple of minutes, your application will send metrics to [one.newrelic.com](https://one.newrelic.com).                  
+    </Step>
+    <Step>
+
+## Find your data 
+
+You can choose our pre-built dashboard template named `Windows services integration ` to monitor your Windows services. Follow these steps to use our pre-built dashboard template:
+
+  1. From [one.newrelic.com](https://one.newrelic.com), go to the <DoNotTranslate>**+ Add data**</DoNotTranslate> page. 
+  2. Click on <DoNotTranslate>**Dashboards**</DoNotTranslate>.
+  3. In the search bar, type `Windows services`. 
+  4. The Windows services dashboard should appear. Click on it to install it.
+
+Your Windows services dashboard is considered a custom dashboard and can be found in the <DoNotTranslate>**Dashboards**</DoNotTranslate> UI. For docs on using and editing dashboards, see [our dashboard docs](/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards).
+    </Step>
+</Steps>
 
 ## Set up an alert [#set-alerts]