fixing broken bookmarks

Author: paulth1

articles/azure-monitor/logs/data-ingestion-time.md

@@ -57,7 +57,7 @@ Network conditions might negatively affect the latency of this data to reach an
 Azure data adds more time to become available at an Azure Monitor Logs ingestion point for processing:
 
 - **Azure platform metrics** are available in under a minute in the metrics database, but they take another 3 minutes to be exported to the Azure Monitor Logs ingestion point.
-- **Resource logs** typically add 30 to 90 seconds, depending on the Azure service. Some Azure services (specifically, Azure SQL Database and Azure Virtual Network) currently report their logs at 5-minute intervals. Work is in progress to improve this time further. To examine this latency in your environment, see the [query that follows](#checking-ingestion-time).
+- **Resource logs** typically add 30 to 90 seconds, depending on the Azure service. Some Azure services (specifically, Azure SQL Database and Azure Virtual Network) currently report their logs at 5-minute intervals. Work is in progress to improve this time further. To examine this latency in your environment, see the [query that follows](#check-ingestion-time).
 - **Activity log** data is ingested in 30 seconds when you use the recommended subscription-level diagnostic settings to send them into Azure Monitor Logs. They might take 10 to 15 minutes if you instead use the legacy integration.
 
 ### Management solutions collection

articles/azure-monitor/logs/queries.md

@@ -78,7 +78,7 @@ The query interface is populated with the following types of queries:
 > Legacy queries are only available in a Log Analytics workspace.
 
 ## Effect of query scope
-The queries that are available when you open Log Analytics are determined by the current [query scope ](scope.md). For example:
+The queries that are available when you open Log Analytics are determined by the current [query scope](scope.md). For example:
 
 - **Workspace**: All example queries and queries from query packs. Legacy queries in the workspace.
 - **Single resource**: Example queries and queries from query packs for the resource type.

articles/azure-monitor/logs/query-packs.md

@@ -74,7 +74,7 @@ Each query in the query pack has the following properties.
 | description | Description of the query displayed in Log Analytics for each query. |
 | body        | Query written in KQL. |
 | related     | Related categories, resource types, and solutions for the query. Used for grouping and filtering in Log Analytics by the user to help locate their query. Each query can have up to ten of each type. Retrieve allowed values from  https://api.loganalytics.io/v1/metadata?select=resourceTypes,solutions,categories. |
-| tags        | Additional tags used by the user for sorting and filtering in Log Analytics. Each tag will be added to Category, Resource Type, and Solution when [grouping and filtering queries](queries.md#finding-and-filtering-queries). |
+| tags        | Additional tags used by the user for sorting and filtering in Log Analytics. Each tag will be added to Category, Resource Type, and Solution when [grouping and filtering queries](queries.md#find-and-filter-queries). |
 
 ## Create a query pack
 You can create a query pack using the REST API or from the **Log Analytics query packs** pane in the Azure portal. Currently the **Log Analytics query packs** pane shows up under **Other** category of **All services** page in the Azure portal.