TCP API Update

Updated the directions in the doc to remove step #4 since it was unnecessary and didn't match our blog on the same topic.

src/content/docs/logs/log-management/log-api/use-tcp-endpoint-forward-logs-new-relic.mdx

@@ -40,12 +40,7 @@ To forward logs to New Relic with `rsyslog`:
    )
    ```
 3. In the `/etc/rsyslog.d/` directory, create a text file named `newrelic.conf`.
-4. Explicitly include the newly created `newrelic.conf` to the `/etc/rsyslog.d/` file:
-
-   ```
-   include(file="/etc/rsyslog.conf.d/newrelic.conf")
-   ```
-5. Add the following to `newrelic.conf`, replacing `YOUR_INSERT_KEY` with your New Relic [Insights API Insert key](/docs/telemetry-data-platform/ingest-manage-data/ingest-apis/use-event-api-report-custom-events#register):
+4. Add the following to `newrelic.conf`, replacing `YOUR_INSERT_KEY` with your New Relic [Insights API Insert key](/docs/telemetry-data-platform/ingest-manage-data/ingest-apis/use-event-api-report-custom-events#register):
 
    ```
    ## Specify each of the files to be tailed in case step 1 is done
@@ -77,12 +72,12 @@ To forward logs to New Relic with `rsyslog`:
           StreamDriverMode="1"
    )
    ```
-6. Restart the `rsyslog` service by running:
+5. Restart the `rsyslog` service by running:
 
    ```
    sudo systemctl restart rsyslog
    ```
-7. [Check your New Relic account](/docs/logs/log-management/ui-data/explore-your-data-log-analytics) for logs.
+6. [Check your New Relic account](/docs/logs/log-management/ui-data/explore-your-data-log-analytics) for logs.
 
 ## Legacy config file for rsyslog 7 or earlier [#legacy-rsyslog]