Merge branch 'main' into tcarter-RelatedContent-Logs

Author: Tracey Carter

gdi/monitors-monitoring/jaeger-grpc.rst

@@ -4,7 +4,7 @@ Jaeger gRPC
 ===========
 
 .. meta::
-   :description: Use this Splunk Observability Cloud integration for the Jaeger gRCP monitor. See benefits, install, configuration, and metrics
+   :description: Use this Splunk Observability Cloud integration for the Jaeger gRPC monitor. See benefits, install, configuration, and metrics
 
 The Splunk Distribution of OpenTelemetry Collector uses the Smart Agent receiver with the
 ``jaeger-grpc`` monitor type to run a gRPC server that listens for

gdi/opentelemetry/collector-common-config.rst

@@ -13,7 +13,7 @@ Common configuration options
     :hidden:
 
     Authentication settings <common-config/collector-common-config-auth.rst>
-    gRCP settings <common-config/collector-common-config-grcp.rst>
+    gRPC settings <common-config/collector-common-config-grpc.rst>
     HTTP settings <common-config/collector-common-config-http.rst>
     Network settings <common-config/collector-common-config-net.rst>
     TLS settings <common-config/collector-common-config-tls.rst>

gdi/opentelemetry/common-config/collector-common-config-grcp.rst renamed to gdi/opentelemetry/common-config/collector-common-config-grpc.rst

@@ -1,7 +1,7 @@
 .. _collector-common-config-grcp:
 
 *********************************************************************************
-Configure gRCP 
+Configure gRPC 
 *********************************************************************************
 
 gRPC exposes a variety of settings you can adjust within individual receivers or exporters of the Collector. 
@@ -10,18 +10,18 @@ gRPC exposes a variety of settings you can adjust within individual receivers or
 
    To configure transport, see :ref:`collector-common-config-net`.
 
-Configure gRCP clients 
+Configure gRPC clients 
 =============================================================================================
 
-To configure gRCP clients in :ref:`exporters <otel-components-exporters>` use these settings:
+To configure gRPC clients in :ref:`exporters <otel-components-exporters>` use these settings:
 
 * ``auth``. See :ref:`collector-common-config-auth`
 
 * ``balancer_name`` 
 
   * Defaults: ``pick_first`` before version 0.103.0, ``round_robin`` for v0.103.0 or higher 
 
-  * Learn more at gRCP's :new-page:`Load Balancing README <https://github.com/grpc/grpc-go/blob/master/examples/features/load_balancing/README.md>`. 
+  * Learn more at gRPC's :new-page:`Load Balancing README <https://github.com/grpc/grpc-go/blob/master/examples/features/load_balancing/README.md>`. 
 
 * ``compression`` 
 
@@ -58,10 +58,10 @@ For example:
             test1: "value1"
             "test 2": "value 2"
 
-Configure gRCP servers 
+Configure gRPC servers 
 =============================================================================================
 
-To configure gRCP servers in :ref:`collector receivers <otel-components-receivers>` use these settings:
+To configure gRPC servers in :ref:`collector receivers <otel-components-receivers>` use these settings:
 
 * ``auth``. See :ref:`collector-common-config-auth`
 
@@ -83,4 +83,4 @@ Learn more
 For more details on the available settings refer to: 
 
 * :new-page:`gRPC Configuration Settings <https://github.com/open-telemetry/opentelemetry-collector/tree/main/config/configgrpc>` in OTel's GitHub repo
-* :new-page:`Golang's gRCP documentation <https://pkg.go.dev/google.golang.org/grpc>`
+* :new-page:`Golang's gRPC documentation <https://pkg.go.dev/google.golang.org/grpc>`

gdi/opentelemetry/deployment-modes.rst

@@ -116,10 +116,10 @@ The Collector for Kubernetes has different deployment options. You can configure
 
 The main deployment modes are:
 
-* Default, which includes the ``agent`` deamonset and the ``clusterReceiver`` deployment component.
-* All collector modes, which includes ``agent`` deamonset, and the ``clusterReceiver`` and the ``gateway`` components.
+* Default, which includes the ``agent`` DaemonSet and the ``clusterReceiver`` deployment component.
+* All collector modes, which includes ``agent`` DaemonSet, and the ``clusterReceiver`` and the ``gateway`` components.
 
-By default, the ``agent`` daemonset deploys a pod running the OpenTelemetry Collector agent in each node of your Kubernetes cluster. The agent pods gather data from your applications, services, and other objects running in their respective nodes, then send the data to Splunk Observability Cloud.
+By default, the ``agent`` DaemonSet deploys a pod running the OpenTelemetry Collector agent in each node of your Kubernetes cluster. The agent pods gather data from your applications, services, and other objects running in their respective nodes, then send the data to Splunk Observability Cloud.
 
 .. image:: /_images/gdi/k8s-daemonset.png
    :width: 40%