Skip to content

Commit f75fba3

Browse files
committed
minor edits
1 parent 851d734 commit f75fba3

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/migrate/tutorial-discover-mysql-database-instances.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ In this tutorial, you learn how to:
1919
2020

2121
> [!NOTE]
22-
> - A Kubernetes-based appliance is required to discover MySQL database instances [Learn more].(migrate-appliance.md) about scenarios covered by a Windows-based appliance.
22+
> - A Kubernetes-based appliance is required to discover MySQL database instances. [Learn more] (migrate-appliance.md) about scenarios covered by a Windows-based appliance.
2323
> - This tutorial shows you the quickest path for trying out a scenario. They use default options where possible.
2424
2525

@@ -58,7 +58,7 @@ The following table lists the regions that support MySQL Discovery and Assessmen
5858

5959
## Set up Kubernetes-based appliance
6060

61-
After you have performed server discovery and software inventory using the Azure Migrate appliance, follow these steps to enable discovery of MySQL database instances by setting up a Kubernetes appliance:
61+
After you performed the server discovery and software inventory using the Azure Migrate appliance, follow these steps to enable discovery of MySQL database instances by setting up a Kubernetes appliance:
6262

6363
### Onboard Kubernetes-based appliance
6464

@@ -112,7 +112,7 @@ After you have performed server discovery and software inventory using the Azure
112112

113113
### Connect using an outbound proxy server
114114

115-
If your machine is behind an outbound proxy server, requests must be routed via the outbound proxy server. Follow these steps to provide proxy settings:
115+
If your machine is behind an outbound proxy server, requests must be routed via the outbound proxy server. To provide proxy settings, follow these steps:
116116

117117
1. Open the terminal on the server and execute the following command to set up environment variables as a root user: `sudo su -`
118118
1. On the deployment machine, set the environment variables needed for `deploy.sh` to use the outbound proxy server:

0 commit comments

Comments
 (0)