Edits

Author: aurbiztondo-splunk

gdi/opentelemetry/automatic-discovery/k8s/k8s-third-party.rst

@@ -13,7 +13,7 @@ You can use automatic discovery to find third-party applications (such as databa
 
   Update the Collector to version 0.94.0 and higher to activate automatic service discovery.
 
-  If you're using the Collector version 0.109.0 or higher, log in to Splunk Observability Cloud and go to the :guilabel:`Discovered services` tab in the :guilabel:`Data Management` menu to see which of your services and third-party applications the Collector has detected and can monitor automatically.   
+  If you're using the Collector version 0.109.0 or higher, log in to Splunk Observability Cloud and go to the :guilabel:`Discovered services` tab in the :guilabel:`Data Management` menu to see which of your services and third-party applications the Collector has detected and can monitor automatically.   See :ref:`discovery-mode-k8s` for more details.
 
 How automatic discovery works
 ================================================
@@ -33,7 +33,7 @@ Deploy the Collector with automatic discovery
 
 You can configure the DaemonSet from the Splunk Distribution of the OpenTelemetry Collector for Kubernetes to run in discovery mode. Edit the properties to add required credentials or service-specific information.
 
-.. note:: To activate auto-discovery in the UI use ``featureGates: splunk.continuousDiscovery``.    
+.. note:: If you're using the Collector version 0.109.0 or higher, activate auto-discovery in the UI using ``featureGates: splunk.continuousDiscovery``.    
 
 The following example shows how to activate discovery mode in the Helm chart and adds authentication properties for PostgreSQL service discovery: