chore(docs): links NR logs Kubernetes plugin to install/uninstall met…

…hods of the Kubernetes integration

src/content/docs/logs/forward-logs/kubernetes-plugin-log-forwarding.mdx

@@ -15,22 +15,17 @@ redirects:
   - /docs/logs/enable-log-management-new-relic/enable-log-monitoring-new-relic/kubernetes-plugin-log-forwarding
 ---
 
-If your log data is already being monitored by [Fluent Bit](https://fluentbit.io/), you can use our [Fluent Bit output plugin](https://github.com/newrelic/newrelic-fluent-bit-output) to forward and enrich your log data in New Relic. This plugin is also provided in a standalone Docker image that can be installed in a [Kubernetes](https://kubernetes.io/) cluster in the form of a [DaemonSet](https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/). We refer to this as our Kubernetes plugin.
+New Relic offers an output [plugin](https://github.com/newrelic/newrelic-fluent-bit-output) for [Fluent Bit](https://fluentbit.io/)to easily forward your logs to [New Relic Logs](https://docs.newrelic.com/docs/logs/new-relic-logs/get-started/introduction-new-relic-logs). This plugin is also provided in a standalone Docker image that can be installed in a [Kubernetes](https://kubernetes.io/) cluster in the form of a [DaemonSet](https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/). We refer to this as our **Kubernetes plugin** for log forwarding.
 
 Forwarding your Kubernetes logs to New Relic will give you enhanced log management capabilities to collect, process, explore, query, and alert on your log data.
 
 ## Enable Kubernetes for log management [#enable-process]
 
-To forward your logs to New Relic with our Kubernetes plugin for Fluent Bit:
+To forward your Kubernetes logs to New Relic with our plugin:
 
-1. Make sure you have:
-
-* An <InlinePopover type="licenseKey" />
-* [Kubernetes](https://kubernetes.io/docs/setup/) cluster deployed
-
-2. Follow the procedures in GitHub to [install the Kubernetes plugin](https://github.com/newrelic/helm-charts/tree/master/charts/newrelic-logging#installation).
-3. Optional: If you are installing the plugin as a Helm chart, you can set [numerous configurations](https://github.com/newrelic/helm-charts/tree/master/charts/newrelic-logging#configuration). However, we recommend the standard setup, as it is valid for most users.
-4. Generate some traffic and wait a few minutes, then [check your account](#find-data) for data.
+1. Install the New Relic Kubernetes integration following the steps from [this page](/docs/kubernetes-pixie/kubernetes-integration/installation/kubernetes-integration-install-configure/). This integration includes the Kubernetes plugin for logs.
+2. Optionally, you can further tune your installation in [Step 3 from the guided install](/docs/kubernetes-pixie/kubernetes-integration/installation/kubernetes-integration-install-configure/#kubernetes-install-navigation) using the numerous configuration options available in the [newrelic-logging repository](https://github.com/newrelic/helm-charts/tree/master/charts/newrelic-logging#configuration). However, we recommend the standard setup, as it is valid for most users.
+3. Generate some traffic and wait a few minutes, then [check your account](#find-data) for data.
 
 <InstallFeedback />
 
@@ -57,4 +52,4 @@ Explore logging data across your platform with our [Logs UI](/docs/logs/log-mana
 
 ## Disable log forwarding [#disable]
 
-To disable log forwarding capabilities, follow standard procedures in [Kubernetes documentation](https://github.com/newrelic/helm-charts/tree/master/charts/newrelic-logging#installation). You do not need to do anything else in New Relic.
+To disable log forwarding capabilities, you can uninstall the Kubernetes plugin by following the steps outlined [here](/docs/kubernetes-pixie/kubernetes-integration/uninstall-kubernetes/). You do not need to do anything else in New Relic.