From 532a027506ecb469f4c7a5576974dda374efa1ed Mon Sep 17 00:00:00 2001
From: HEMAGUNNALA <hgunnala@newrelic.com>
Date: Mon, 28 Oct 2024 19:06:45 +0530
Subject: [PATCH] resolve workflow errors

---
 .../logs/forward-logs/fluent-bit-plugin-log-forwarding.mdx  | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/src/content/docs/logs/forward-logs/fluent-bit-plugin-log-forwarding.mdx b/src/content/docs/logs/forward-logs/fluent-bit-plugin-log-forwarding.mdx
index 8db91f72e01..b88c1ffcd38 100644
--- a/src/content/docs/logs/forward-logs/fluent-bit-plugin-log-forwarding.mdx
+++ b/src/content/docs/logs/forward-logs/fluent-bit-plugin-log-forwarding.mdx
@@ -25,7 +25,7 @@ Forwarding your Fluent Bit logs to New Relic will give you enhanced <InlinePopov
 
 ## Kubernetes installation[#Kubernetes-installation]
 
-New Relic has a [Fluent Bit](https://fluentbit.io/) [output plugin](https://github.com/newrelic/newrelic-fluent-bit-output) to forward your logs to New Relic log management. This plugin is also provided in a standalone Docker image that can be installed in a Kubernetes cluster in the form of a DaemonSet, also known as the Kubernetes plugin.
+New Relic has a [Fluent Bit](https://fluentbit.io/) [output plugin](https://github.com/newrelic/newrelic-fluent-bit-output) to forward your logs to New Relic log management. You can install this plugin as a standalone Docker image in a Kubernetes cluster, where it functions as a DaemonSet, also known as the Kubernetes plugin.
 
 You can install it in your cluster using our Helm chart in two ways.
 
@@ -53,12 +53,10 @@ Go here for [uninstallation instructions](/docs/kubernetes-pixie/kubernetes-inte
 
 ### Using Docker Image 
 
-we've published a container with the plugin installed. It serves as a base image to be used by our Kubernetes integration. If you have your own custom kubernetes integration, we recommend you use our [docker image](https://hub.docker.com/r/newrelic/newrelic-fluentbit-output) that comes with the [New Relic’s fluent bit output plugin](https://github.com/newrelic/newrelic-fluent-bit-output) or use the docker image as a base image and layer your own custom configuration files.
+we've published a container with the plugin installed , serves as a base image for our Kubernetes integration. If you have your own custom kubernetes integration, we recommend you use our [docker image](https://hub.docker.com/r/newrelic/newrelic-fluentbit-output) that comes with the [New Relic’s fluent bit output plugin](https://github.com/newrelic/newrelic-fluent-bit-output) . Alternatively, you can use the docker image as a base image and layer your own custom configuration files.
 
 ## On-host installation[#On-host-installation]
 
-we've published a container with the plugin installed. It serves as a base image to be used by our Kubernetes integration. We recommend you use this base image and layer your own custom configuration files.
-
 ## Install the Fluent Bit plugin [#fluentbit-plugin]
 
 To install the Fluent Bit plugin: