fixes

Author: bwren

articles/azure-monitor/essentials/data-collection-rule-overview.md

@@ -48,7 +48,7 @@ With direct ingestion, a particular DCR is specified to process the incoming dat
 [Transformations](./data-collection-transformations.md) allow you to modify incoming data before it's stored in Azure Monitor. You may filter unneeded data to reduce your ingestion costs, remove sensitive data that shouldn't be persisted in the Log Analytics workspace, or format data to ensure that it matches the schema of its destination. Transformations are [KQL queries](../logs/log-query-overview.md) defined in the DCR that run in the cloud pipeline.
 
 ## Endpoints
-Data sent to the cloud pipeline must be sent to the URL of a specific endpoint. Depending on the scenario, this may be a public endpoint, an endpoint provided by the DCR itself, or a data collection endpoint (DCE) that you create in your Azure subscription. See [Data collection endpoints in Azure Monitor](./data-collection-endpoints.md) for details on the endpoints used in different data collection scenarios.
+Data sent to the cloud pipeline must be sent to the URL of a specific endpoint. Depending on the scenario, this may be a public endpoint, an endpoint provided by the DCR itself, or a data collection endpoint (DCE) that you create in your Azure subscription. See [Data collection endpoints in Azure Monitor](./data-collection-endpoint-overview.md) for details on the endpoints used in different data collection scenarios.
 
 ## Edge pipeline
 The [edge pipeline](./edge-pipeline-configure.md) extends the Azure Monitor pipeline to your own data center. It enables at-scale collection and routing of telemetry data before it's delivered to Azure Monitor in the Azure cloud. 

articles/azure-monitor/essentials/data-collection-rule-view.md

@@ -75,7 +75,7 @@ The **Resources** view lists all Azure resources that match the selected filter,
 
 The **Data collection rules** column represents the number of DCRs that are associated with each resource. Click this value to open a new pane listing the DCRs associated with the resource. 
 
-:::image type="content" source="media/data-collection-rule-view/resources-view-association.png" alt-text="Screenshot of the DCR associations for a resource in the resources view in  the preview experience for DCRs in the Azure portal." lightbox="media/data-collection-rule-view/resources-view-association.png":::
+:::image type="content" source="media/data-collection-rule-view/resources-view-associations.png" alt-text="Screenshot of the DCR associations for a resource in the resources view in  the preview experience for DCRs in the Azure portal." lightbox="media/data-collection-rule-view/resources-view-associations.png":::
 
 > [!IMPORTANT]
 > Not all DCRs are associated with resources. For example, DCRs used with the [Logs ingestion API](../logs/logs-ingestion-api-overview.md) are specified in the API call and do not use associations. These DCRs still appear in the view, but will have a **Resource Count** of 0.

articles/azure-monitor/toc.yml

@@ -621,17 +621,17 @@ items:
     href: data-sources.md
   - name: Data collection methods
     items:
-    - name: Data collection rules
+    - name: Data collection rules (DCR)
       items:
       - name: Overview
-        displayName: data collection, pipeline
+        displayName: data collection rule, dcr, Azure Monitor pipeline
         href: essentials/data-collection-rule-overview.md
       - name: Best practices
         displayName: data collection, data collection rules
         href: essentials/data-collection-rule-best-practices.md
-      - name: View rules
+      - name: View DCRs
         href: essentials/data-collection-rule-view.md
-      - name: Create and edit
+      - name: Create and edit DCRs
         items:
         - name: Create
           displayName: Data collection rules