Fixes

Author: aurbiztondo-splunk

gdi/opentelemetry/collector-windows/install-windows-msi.rst

@@ -177,7 +177,7 @@ Custom MSI URLs
 
 By default, the Collector MSI is downloaded from :new-page:`https://dl.signalfx.com <https://dl.signalfx.com>`. 
 
-To specify custom URLs for these downloads, replace ``COLLECTOR_MSI_URL``with the URLs to the desired MSI packages to install:
+To specify custom URLs for these downloads, replace ``COLLECTOR_MSI_URL`` with the URL to the desired MSI packages to install:
 
 .. code-block:: PowerShell
 

gdi/opentelemetry/components/fluentd-receiver.rst

@@ -7,21 +7,15 @@ Fluent Forward receiver
 .. meta::
       :description: The Fluent Forward receiver allows the Splunk Distribution of OpenTelemetry Collector to collect logs and events using the Fluent Forward protocol.
 
+.. caution:: ``fluentd``` will be deprecated in October 2025. In Kubernetes environments use native OpenTelemetry log collection instead. In Linux and Windows platforms use the Universal Forwarder. See :ref:otel-config-logs`.
+
 The Fluent Forward receiver allows the Splunk Distribution of the OpenTelemetry Collector to collect events using the bundled Fluentd application. The supported pipeline type is ``logs``. See :ref:`otel-data-processing` for more information.
 
 The receiver accepts data formatted as Fluent Forward events through a TCP connection. All three Fluent event types, message, forward, and packed forward, are supported, including compressed packed forward.
 
-.. caution:: Fluentd is deactivated by default for Linux and Windows. To activate it, use the ``--with-fluentd`` option when installing the Collector for Linux, or the ``with_fluentd = 1`` option when installing the Collector for Windows.
-
 Get started
 ======================
 
-.. note:: 
-  
-  This component is included in the default configuration of the Splunk Distribution of the OpenTelemetry Collector when deploying in host monitoring (agent) mode. See :ref:`otel-deployment-mode` for more information. 
-  
-  For details about the default configuration, see :ref:`otel-kubernetes-config`, :ref:`linux-config-ootb`, or :ref:`windows-config-ootb`. You can customize your configuration any time as explained in this document.
-
 Follow these steps to configure and activate the component:
 
 1. Deploy the Splunk Distribution of the OpenTelemetry Collector to your host or container platform:
@@ -33,7 +27,7 @@ Follow these steps to configure and activate the component:
 2. Configure the receiver as described in the next document.
 3. Restart the Collector.
 
-By default, the Splunk Distribution of the OpenTelemetry Collector includes the Fluent Forward receiver in the ``logs`` pipeline:
+Next, add the Fluent Forward receiver in the ``logs`` pipeline:
 
 .. code-block:: yaml
 
@@ -46,12 +40,6 @@ By default, the Splunk Distribution of the OpenTelemetry Collector includes the
       logs:
         receivers: [fluentforward]
 
-For more information on how to install Fluentd when manually installing the Collector, see:
-
-* :ref:`fluentd-manual-config-linux`
-* :ref:`fluentd-manual-config-windows`
-* :ref:`windows-manual-fluentd`
-
 Settings
 ======================
 
@@ -64,9 +52,12 @@ The following table shows the configuration options for the Fluent Forward recei
 Troubleshooting
 ======================
 
-For troubleshooting Fluentd, see:
+.. raw:: html
+
+   <div class="include-start" id="troubleshooting-components.rst"></div>
 
-* :ref:`fluentd-collector-troubleshooting`
-* :ref:`otel-linux-uninstall-both-otel-and-tdagent`
+.. include:: /_includes/troubleshooting-components.rst
+
+.. raw:: html
 
-.. caution:: If you wish to collect logs for the target host with Fluentd, make sure Fluentd is installed and turned on in your Collector instance.
+   <div class="include-stop" id="troubleshooting-components.rst"></div>