Skip to content

Commit 84369bd

Browse files
authored
Merge pull request #124366 from Rageking8/add-missing-space-before-links
Add missing space before links
2 parents 750fde8 + e554d12 commit 84369bd

18 files changed

+20
-25
lines changed

articles/automation/automation-disaster-recovery.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,7 @@ You can use these scripts for migration of Automation account assets from the ac
9393
1. Ensure that both the source and destination Automation accounts should belong to the same Microsoft Entra tenant.
9494

9595
### Create and execute the runbook
96-
You can use the[PowerShell script](https://github.com/azureautomation/Migrate-automation-account-assets-from-one-region-to-another) or [PowerShell workflow](https://github.com/azureautomation/Migrate-automation-account-assets-from-one-region-to-another-PwshWorkflow/tree/main) runbook or import from the Runbook gallery and execute it to enable migration of assets from one Automation account to another.
96+
You can use the [PowerShell script](https://github.com/azureautomation/Migrate-automation-account-assets-from-one-region-to-another) or [PowerShell workflow](https://github.com/azureautomation/Migrate-automation-account-assets-from-one-region-to-another-PwshWorkflow/tree/main) runbook or import from the Runbook gallery and execute it to enable migration of assets from one Automation account to another.
9797

9898
Follow the steps to import and execute the runbook:
9999

articles/automation/automation-scenario-aws-deployment.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -95,7 +95,7 @@ Ensure that the AWS PowerShell module has been imported into Azure Automation.
9595
9696
## Next steps
9797
98-
* To find out what runbooks are supported, see[Azure Automation runbook types](automation-runbook-types.md).
98+
* To find out what runbooks are supported, see [Azure Automation runbook types](automation-runbook-types.md).
9999
* To work with runbooks, see [Manage runbooks in Azure Automation](manage-runbooks.md).
100100
* For details of PowerShell, see [PowerShell Docs](/powershell/scripting/overview).
101101
* For script support, see [Native PowerShell script support in Azure Automation](https://azure.microsoft.com/blog/announcing-powershell-script-support-azure-automation-2/).

articles/container-registry/container-registry-manage-artifact.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@ az login
5858
az acr login -n $REGISTRY
5959
```
6060

61-
If Docker isn't available, you can utilize the AD token provided for authentication. Authenticate with your[individual Microsoft Entra identity](container-registry-authentication.md?tabs=azure-cli#individual-login-with-azure-ad) using an AD token. Always use "000..." for the `USER_NAME` as the token is parsed through the `PASSWORD` variable.
61+
If Docker isn't available, you can utilize the AD token provided for authentication. Authenticate with your [individual Microsoft Entra identity](container-registry-authentication.md?tabs=azure-cli#individual-login-with-azure-ad) using an AD token. Always use "000..." for the `USER_NAME` as the token is parsed through the `PASSWORD` variable.
6262

6363
```azurecli
6464
# Login to Azure
@@ -528,5 +528,3 @@ In this article, you learned how to use Azure Container Registry to store, manag
528528
[iana-mediatypes]: https://www.rfc-editor.org/rfc/rfc6838
529529
[acr-landing]: https://aka.ms/acr
530530
[Notation]: /azure/container-registry/container-registry-tutorial-sign-build-push
531-
532-

articles/dns/dns-faq-private.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -101,7 +101,7 @@ sections:
101101
- question: |
102102
How do I migrate my existing private DNS zones to the new model?
103103
answer: |
104-
We strongly recommend that you migrate to the new resource model as soon as possible. Legacy resource model will be supported, however, further features won't be developed on top of this model. In future, we intend to deprecate it in favor of new resource model. For guidance on how to migrate your existing private DNS zones to new resource model see[migration guide for Azure DNS private zones](private-dns-migration-guide.md).
104+
We strongly recommend that you migrate to the new resource model as soon as possible. Legacy resource model will be supported, however, further features won't be developed on top of this model. In future, we intend to deprecate it in favor of new resource model. For guidance on how to migrate your existing private DNS zones to new resource model see [migration guide for Azure DNS private zones](private-dns-migration-guide.md).
105105
106106
- question: |
107107
Which one takes precedence, Azure private DNS or a custom DNS server setup on a VM?

articles/event-grid/authenticate-with-entra-id-namespaces.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ The identity used to publish events to Event Grid must have the permission ``Mic
6161
With RBAC privileges taken care of, you can now [build your client application to send events](#publish-events-using-event-grids-client-sdks) to Event Grid.
6262

6363
> [!NOTE]
64-
> Event Grid supports more RBAC roles for purposes beyond sending events. For more information, see[Event Grid built-in roles](security-authorization.md#built-in-roles).
64+
> Event Grid supports more RBAC roles for purposes beyond sending events. For more information, see [Event Grid built-in roles](security-authorization.md#built-in-roles).
6565
6666

6767
## Publish events using Event Grid's client SDKs

articles/event-grid/authenticate-with-microsoft-entra-id.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,7 @@ The identity used to publish events to Event Grid must have the permission ``Mic
6464
With RBAC privileges taken care of, you can now [build your client application to send events](#publish-events-using-event-grids-client-sdks) to Event Grid.
6565

6666
> [!NOTE]
67-
> Event Grid supports more RBAC roles for purposes beyond sending events. For more information, see[Event Grid built-in roles](security-authorization.md#built-in-roles).
67+
> Event Grid supports more RBAC roles for purposes beyond sending events. For more information, see [Event Grid built-in roles](security-authorization.md#built-in-roles).
6868
6969

7070
## Publish events using Event Grid's client SDKs

articles/frontdoor/classic-retirement-faq.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ Azure Front Door (classic) is a legacy service that provides dynamic site accele
3232
Azure Front Door Standard and Premium tiers represent the enhanced versions of Azure Front Door (classic). They maintain the same Service Level Agreement (SLA) and offer more benefits, including:
3333

3434
* A unified static and dynamic delivery platform, with simplified cost model.
35-
* Enhanced security features, such as[Private Link integration](private-link.md), advanced WAF enhancements with DRS 2.1, anomaly scoring based detection and bot management, and many more to come.
35+
* Enhanced security features, such as [Private Link integration](private-link.md), advanced WAF enhancements with DRS 2.1, anomaly scoring based detection and bot management, and many more to come.
3636
* Deep integration with Azure services to deliver secure, accelerated, and user friendly end-to-end cloud solutions. These integrations include:
3737
* DNS deterministic name library integrations to prevent subdomain take over
3838
* [Prevalidated domain integration with PaaS service with one-time domain validation](./standard-premium/how-to-add-custom-domain.md#associate-the-custom-domain-with-your-azure-front-door-endpoint).

articles/hdinsight/hadoop/apache-hadoop-use-hive-visual-studio.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -145,4 +145,4 @@ As you can see, the HDInsight tools for Visual Studio provide an easy way to wor
145145
146146
* For information about other ways you can work with Hadoop on HDInsight, see [Use MapReduce in Apache Hadoop on HDInsight](hdinsight-use-mapreduce.md)
147147
148-
* For more information about the HDInsight tools for Visual Studio, see[Use Data Lake Tools for Visual Studio to connect to Azure HDInsight and run Apache Hive queries](apache-hadoop-visual-studio-tools-get-started.md)
148+
* For more information about the HDInsight tools for Visual Studio, see [Use Data Lake Tools for Visual Studio to connect to Azure HDInsight and run Apache Hive queries](apache-hadoop-visual-studio-tools-get-started.md)

articles/iot/concepts-modeling-guide.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -675,7 +675,7 @@ IoT Central implements more versioning rules for device models. If you version a
675675

676676
### Publish
677677

678-
As of February 2024, the Azure Certified Device program is retired. Therefore, Microsoft is no longer accepting submissions of DTDL models to the[Azure IoT plug and play models](https://github.com/Azure/iot-plugandplay-models) repository.
678+
As of February 2024, the Azure Certified Device program is retired. Therefore, Microsoft is no longer accepting submissions of DTDL models to the [Azure IoT plug and play models](https://github.com/Azure/iot-plugandplay-models) repository.
679679

680680
If you want to set up your own model repository, you can use the [Azure IoT plug and play models tools](https://github.com/Azure/iot-plugandplay-models-tools) repository. This repository includes the code for the `dmr-client` CLI tool that can validate, import, and expand DTDL models. This tool also lets you index model repositories that follow the device model repository conventions.
681681

articles/notification-hubs/notification-hubs-push-bing-spatial-data-geofencing-notification.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,6 @@ author: sethmanheim
77
manager: femila
88
editor: jwargo
99

10-
ms.assetid: f41beea1-0d62-4418-9ffc-c9d70607a1b7
1110
ms.service: azure-notification-hubs
1211
ms.tgt_pltfrm: mobile-windows-phone
1312
ms.devlang: csharp
@@ -158,7 +157,7 @@ In this tutorial, you take the following steps:
158157
}
159158
```
160159
161-
To learn more about getting the user's location in UWP apps, see[Get the user's location](/windows/uwp/maps-and-location/get-location).
160+
To learn more about getting the user's location in UWP apps, see [Get the user's location](/windows/uwp/maps-and-location/get-location).
162161
5. To check that the location acquisition is actually working, open the code side of your main page (`MainPage.xaml.cs`). Create a new event handler for the `Loaded` event in the `MainPage` constructor.
163162
164163
```csharp

0 commit comments

Comments
 (0)