fix

Author: mbechtold-splunk

gdi/get-data-in/application/nodejs/breaking-changes.rst

@@ -10,7 +10,7 @@ Splunk OpenTelemetry JS version 3.0 breaking changes
 Update to Splunk OpenTelemetry JS version 3.0
 ==========================================================
 
-To update your Splunk Distribution for OpenTelemetry JS agent to version 3.0, see :ref:`instrument-nodejs-application` and install the latest version of the Splunk OpenTelemetry JS agent.
+To update your Splunk Distribution for OpenTelemetry JS agent to version 3.0, see :ref:`instrument-nodejs-applications-3x` and install the latest version of the Splunk OpenTelemetry JS agent.
 
 Default port and protocol changes
 =================================

gdi/get-data-in/application/nodejs/configuration/advanced-nodejs-otel-configuration.rst

@@ -144,7 +144,7 @@ The following settings control trace sampling:
 
 .. list-table::
    :header-rows: 1
-   :widths: 30 70
+   :widths: 20 40 40
    :width: 100%
 
    * - Environment variable
@@ -155,7 +155,7 @@ The following settings control trace sampling:
      - ``always_on``
    * - OTEL_TRACES_SAMPLER_ARG
      - Semicolon-separated list of rules for the ``rules`` sampler. For example, when setting the sampler to ``parentbased_traceidratio`` you can set the ratio using a number in the 0 to 1 range: |br| |br| ``OTEL_TRACES_SAMPLER_ARG=0.25``.
-     - `` ``
+     - None
 
 
 .. _trace-exporters-settings-nodejs-3x:

gdi/get-data-in/application/nodejs/instrumentation/instrument-nodejs-application.rst

@@ -38,8 +38,6 @@ Install the Splunk Distribution of OpenTelemetry JS manually
 If you don't use the guided setup, follow these instructions to manually install the Splunk Distribution of OpenTelemetry JS:
 
 - :ref:`install-enable-nodejs-agent`
-   - :ref:`enable_profiling_nodejs`
-   - :ref:`enable_automatic_metric_collection_nodejs`
 - :ref:`configure-nodejs-instrumentation`
 - :ref:`nodejs-programmatically-instrument`
 
@@ -151,7 +149,7 @@ To activate automatic runtime metric collection, activate the metrics feature us
 Configure the Node.js distribution
 -----------------------------------------------------
 
-In most cases, the only configuration setting you need to enter is the service name. For advanced configuration, like changing trace propagation formats or configuring server trace data, see :ref:`advanced-nodejs-otel-configuration`.
+In most cases, the only configuration setting you need to enter is the service name. For advanced configuration, such as changing trace propagation formats or configuring server trace data, see :ref:`advanced-nodejs-otel-configuration`.
 
 .. _nodejs-programmatically-instrument-3x:
 

gdi/get-data-in/application/nodejs/performance.rst

@@ -1,13 +1,13 @@
 .. _nodejs-otel-performance-3x:
 
 ***************************************************
-Performance reference for Splunk OTel Node.js agent
+Performance reference for Splunk OTel JS agent
 ***************************************************
 
 .. meta::
    :description: Minimum requirements of the Splunk OTel Node.js agent, as well as potential constraints impacting performance, and guidelines to optimize and troubleshoot the performance of the agent.
 
-The Splunk OTel Node.js agent instruments your application at runtime. Like any other software agent, the Node.js agent requires system resources like CPU, memory, and network bandwidth. The use of resources by the agent is called agent overhead or performance overhead. The Splunk OTel Node.js agent has minimal impact on system performance when instrumenting Node.js applications, although the final agent overhead depends on multiple factors.
+The Splunk OTel JS agent instruments your application at runtime. Like any other software agent, the JS agent requires system resources like CPU, memory, and network bandwidth. The use of resources by the agent is called agent overhead or performance overhead. The Splunk OTel Node.js agent has minimal impact on system performance when instrumenting Node.js applications, although the final agent overhead depends on multiple factors.
 
 Some factors that might increase agent overhead are environmental, such as the physical machine architecture, CPU frequency, amount and speed of memory, system temperature, and resource contention. Other factors include virtualization and containerization, the operating system and its libraries, the Node.js version, Node.js configuration, the algorithmic design of the software being monitored, and software dependencies.