diff --git a/gdi/private-connectivity/aws-privatelink.rst b/gdi/private-connectivity/aws-privatelink.rst
index a44cfc70f..0ce0d4c10 100644
--- a/gdi/private-connectivity/aws-privatelink.rst
+++ b/gdi/private-connectivity/aws-privatelink.rst
@@ -315,15 +315,15 @@ To use AWS PrivateLink URLs in your Collector instance, update the necessary var
     - Example
 
   * - Metric ingest endpoint
-    - ``private-ingest.<REGION>.signalfx.com``
+    - ``private-ingest.<realm>.signalfx.com``
     - ``private-ingest.us0.signalfx.com``
 
   * - Traces ingest endpoint
-    - ``private-ingest.<REGION>.signalfx.com/v2/trace``
+    - ``private-ingest.<realm>.signalfx.com/v2/trace``
     - ``private-ingest.us0.signalfx.com/v2/trace``
 
   * - API endpoint URL
-    - ``http://<REGION>.signalfx.com``
+    - ``http://private-api.<realm>.signalfx.com``
     - ``http://private-api.us0.signalfx.com``
 
 
diff --git a/metrics-and-metadata/metrics-usage-analytics.rst b/metrics-and-metadata/metrics-usage-analytics.rst
index 2f7a5da57..c2265504d 100644
--- a/metrics-and-metadata/metrics-usage-analytics.rst
+++ b/metrics-and-metadata/metrics-usage-analytics.rst
@@ -23,7 +23,7 @@ With usage analytics, you can quickly find and visualize which metrics your orga
 Usage analytics can help you complete the following example scenarios: 
 
 * You want to view high-cardinality custom metrics that are taking up large chunks of your metric usage plan. 
-* You want to identify what metrics your team is producing so you can access their usefulness.
+* You want to identify what metrics your team is producing so you can assess their usefulness.
 * You want to find the source and ownership of a certain metric so that you can modify or adjust it.
 
 .. _mua-understand-metrics:
diff --git a/sp-oncall/spoc-integrations/arista-cloudvision-integration.rst b/sp-oncall/spoc-integrations/arista-cloudvision-integration.rst
new file mode 100644
index 000000000..369ee1d51
--- /dev/null
+++ b/sp-oncall/spoc-integrations/arista-cloudvision-integration.rst
@@ -0,0 +1,38 @@
+.. _arista-cloudvision-spoc:
+
+Arista CloudVision for Splunk On-Call
+***************************************************
+
+.. meta::
+    :description: Configure the Arista CloudVision integration for Splunk On-Call.
+
+Arista CloudVision is a multi-domain management platform that uses cloud networking principles to deliver a simplified NetOps experience. 
+
+Requirements
+==================
+
+This integration is compatible with the following versions of Splunk On-Call:
+
+- Starter
+- Growth
+- Enterprise
+
+
+Splunk On-Call configuration
+==============================
+
+#. From the Splunk On-Call web portal, select :guilabel:`Integrations` then :guilabel:`Prometheus`. 
+#. Select  the :guilabel:`Prometheus` integration and copy the :guilabel:`Service API Endpoint` to your clipboard.
+
+CloudVision configuration
+============================
+
+#. In Arista CloudVision, go to :guilabel:`Events` then :guilabel:`Notification Configuration` then :guilabel:`Platforms`.  
+#. Scroll to the :guilabel:`VictorOps` section and paste the Service API Endpoint you previously copied in the :guilabel:`VictorOps API Key` field. Leave the :guilabel:`VictorOps URL` field blank.
+#. Next, configure this platform in a receiver by going to :guilabel:`Events` then :guilabel:`Notification Configuration` then :guilabel:`Receivers`.
+#. Select :guilabel:`Add Receivers`.
+#. Enter the receiver name in the :guilabel:`Receiver Name` field and select :guilabel:`Add Configuration`.  
+#. Select the :guilabel:`VictorOps` option in the table, including the :guilabel:`routing key` you want to notify in Splunk On-Call. For more information on routing keys or instructions on creating a new one, see :ref:`spoc-routing-keys`. If required, select the :guilabel:`Send alert when events are resolved` checkbox.
+#. Next, configure rules to define when the receiver is used. Go to :guilabel:`Events` then :guilabel:`Notification Configuration` then :guilabel:`Rules` and select :guilabel:`Add Rules`. Enter the appropriate settings and select the :guilabel:`VictorOps` receiver.  
+
+For additional information, see the Arista CloudVision documentation at :new-page:`https://www.arista.com/en/cg-cv/cv-accessing-events#task_zxl_5yv_klb`.
diff --git a/sp-oncall/spoc-integrations/integrations-main.rst b/sp-oncall/spoc-integrations/integrations-main.rst
index b418fdbbe..fb2503dc0 100644
--- a/sp-oncall/spoc-integrations/integrations-main.rst
+++ b/sp-oncall/spoc-integrations/integrations-main.rst
@@ -14,6 +14,7 @@ Splunk On-Call integrations
    alertsite-integration
    appdynamics-integration
    appoptics-integration
+   arista-cloudvision-integration
    atatus-integration
    aws-cloudwatch-integration-guide
    azure-monitoring-integration-guide