more changes

Author: mbechtold-splunk

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

@@ -166,7 +166,7 @@ To instrument your application programmatically, add the following lines at the
 
    start({
       serviceName: 'my-node-service',
-      endpoint: 'http://localhost:4317'
+      endpoint: 'http://localhost:4318'
    });
 
    // Rest of your main module
@@ -252,7 +252,7 @@ To deploy the Collector for Node.js in a Kubernetes environment, follow these st
                    fieldRef:
                      fieldPath: status.hostIP
                - name: OTEL_EXPORTER_OTLP_ENDPOINT
-                 value: "http://$(SPLUNK_OTEL_AGENT):4317"
+                 value: "http://$(SPLUNK_OTEL_AGENT):4318"
                - name: OTEL_SERVICE_NAME
                  value: "<serviceName>"
                - name: OTEL_RESOURCE_ATTRIBUTES

gdi/get-data-in/application/nodejs/splunk-nodejs-otel-distribution.rst

@@ -31,7 +31,7 @@ Defaults of the Splunk Distribution of OpenTelemetry JS
 The Splunk Distribution of OpenTelemetry JS has the following default settings for context propagation, exporters, and trace settings:
 
 - W3C tracecontext and W3C baggage context propagation is activated by default. You can also configure B3 propagation. See :ref:`trace-propagation-configuration-nodejs`.
-- The OTLP exporter is configured by default to send spans to the local :ref:`Splunk Distribution of OpenTelemetry Collector <otel-intro>` over gRPC.
+- The OTLP exporter is configured by default to send spans to the local :ref:`Splunk Distribution of OpenTelemetry Collector <otel-intro>` over ``http/protobuf``.
 - Unlimited defaults for trace configuration to support full-fidelity tracing. See :ref:`trace-configuration-nodejs`.
 
 Support for previous versions