Skip to content

Commit 46c717e

Browse files
authored
Merge pull request #263125 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
2 parents c0101aa + da74104 commit 46c717e

File tree

3 files changed

+4
-4
lines changed

3 files changed

+4
-4
lines changed

articles/azure-monitor/visualize/workbooks-jsonpath.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@ In this example, the JSON object represents a store's inventory. We're going to
7373

7474
:::image type="content" source="media/workbooks-jsonpath/query-jsonpath.png" alt-text="Screenshot that shows editing a query item with JSON data source and JSON path result format.":::
7575

76-
## Use regular expressions to covert values
76+
## Use regular expressions to convert values
7777

7878
You may have some data that isn't in a standard format. To use that data effectively, you would want to convert that data into a standard format.
7979

articles/event-hubs/event-hubs-capture-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ The capture feature is included in the premium tier so there is no additional ch
7070
Capture doesn't consume egress quota as it is billed separately.
7171

7272
## Integration with Event Grid
73-
You can create an Azure Event Grid subscription with an Event Hubs namespace as its source. The following tutorial shows you how to create an Event Grid subscription with an event hub as a source and an Azure Functions app as a sink: [Process and migrate captured Event Hubs data to a Azure Synapse Analytics using Event Grid and Azure Functions](store-captured-data-data-warehouse.md).
73+
You can create an Azure Event Grid subscription with an Event Hubs namespace as its source. The following tutorial shows you how to create an Event Grid subscription with an event hub as a source and an Azure Functions app as a sink: [Process and migrate captured Event Hubs data to an Azure Synapse Analytics using Event Grid and Azure Functions](store-captured-data-data-warehouse.md).
7474

7575
## Explore captured files
7676
To learn how to explore captured Avro files, see [Explore captured Avro files](explore-captured-avro-files.md).

articles/virtual-network/subnet-extension.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.author: allensu
1414

1515
Workload migration to the public cloud requires careful planning and coordination. One of the key considerations can be the ability to retain your IP addresses. Which can be important especially if your applications have IP address dependency or you have compliance requirements to use specific IP addresses. Azure Virtual Network solves this problem for you by allowing you to create virtual networks and subnets using an IP address range of your choice.
1616

17-
Migrations can get a bit challenging when the above requirement is coupled with an extra requirement to keep some applications on-premises. In such as a situation, you have to split the applications between Azure and on-premises, without renumbering the IP addresses on either side. Additionally, you have to allow the applications to communicate as if they are in the same network.
17+
Migrations can get a bit challenging when the above requirement is coupled with an extra requirement to keep some applications on-premises. In such a situation, you have to split the applications between Azure and on-premises, without renumbering the IP addresses on either side. Additionally, you have to allow the applications to communicate as if they are in the same network.
1818

1919
One solution to the above problem is subnet extension. Extending a network allows applications to talk over the same broadcast domain when they exist at different physical locations, removing the need to rearchitect your network topology.
2020

@@ -44,4 +44,4 @@ In the above example, the Azure NVA and the on-premises NVA communicate and lear
4444
In the next section, you'll find details on subnet extension solutions we've tested on Azure.
4545

4646
## Next steps
47-
[Extend your on-premises subnets into Azure using Azure Extended Network](/windows-server/manage/windows-admin-center/azure/azure-extended-network).
47+
[Extend your on-premises subnets into Azure using Azure Extended Network](/windows-server/manage/windows-admin-center/azure/azure-extended-network).

0 commit comments

Comments
 (0)