More VS Code edits.

Author: JoshTheTechWriter

articles/spring-apps/basic-standard/how-to-configure-palo-alto.md

@@ -52,7 +52,7 @@ The rest of this article assumes you have the following two pre-configured netwo
 
 Next, create three CSV files.
 
-Name the first file *AzureSpringAppsServices.csv*. This file should contain ingress ports for Azure Spring Apps. The values in the following example are for demonstration purposes only. For all of the required values, see the [Azure Global required network rules](./vnet-customer-responsibilities.md#azure-global-required-network-rules) section of [Customer responsibilities for running Azure Spring Apps in a virtual network](./vnet-customer-responsibilities.md).
+Name the first file **AzureSpringAppsServices.csv**. This file should contain ingress ports for Azure Spring Apps. The values in the following example are for demonstration purposes only. For all of the required values, see the [Azure Global required network rules](./vnet-customer-responsibilities.md#azure-global-required-network-rules) section of [Customer responsibilities for running Azure Spring Apps in a virtual network](./vnet-customer-responsibilities.md).
 
 ```CSV
 name,protocol,port,tag
@@ -63,7 +63,7 @@ ASC_445,tcp,445,AzureSpringApps
 ASC_123,udp,123,AzureSpringApps
 ```
 
-Name the second file *AzureSpringAppsUrlCategories.csv*. This file should contain the addresses (with wildcards) that should be available for egress from Azure Spring Apps. The values in the following example are for demonstration purposes only. For up-to-date values, see the [Azure Global required FQDN / application rules](./vnet-customer-responsibilities.md#azure-global-required-fqdn--application-rules) section of [Customer responsibilities for running Azure Spring Apps in a virtual network](./vnet-customer-responsibilities.md).
+Name the second file **AzureSpringAppsUrlCategories.csv**. This file should contain the addresses (with wildcards) that should be available for egress from Azure Spring Apps. The values in the following example are for demonstration purposes only. For up-to-date values, see the [Azure Global required FQDN / application rules](./vnet-customer-responsibilities.md#azure-global-required-fqdn--application-rules) section of [Customer responsibilities for running Azure Spring Apps in a virtual network](./vnet-customer-responsibilities.md).
 
 ```CSV
 name,description
@@ -81,7 +81,7 @@ crl.microsoft.com,
 crl3.digicert.com
 ```
 
-Name the third file *AzureMonitorAddresses.csv*. This file should contain all addresses and IP ranges to be made available for metrics and monitoring via Azure Monitor, if you're using Azure monitor. The values in the following example are for demonstration purposes only. For up-to-date values, see [IP addresses used by Azure Monitor](/azure/azure-monitor/ip-addresses).
+Name the third file **AzureMonitorAddresses.csv**. This file should contain all addresses and IP ranges to be made available for metrics and monitoring via Azure Monitor, if you're using Azure monitor. The values in the following example are for demonstration purposes only. For up-to-date values, see [IP addresses used by Azure Monitor](/azure/azure-monitor/ip-addresses).
 
 ```CSV
 name,type,address,tag
@@ -127,7 +127,7 @@ $url = "https://${PaloAltoIpAddress}/restapi/v9.1/Objects/ServiceGroups?location
 Invoke-RestMethod -Method Delete -Uri $url -Headers $paloAltoHeaders -SkipCertificateCheck
 ```
 
-Delete each Palo Alto service (as defined in *AzureSpringAppsServices.csv*) as shown in the following example:
+Delete each Palo Alto service (as defined in **AzureSpringAppsServices.csv**) as shown in the following example:
 
 ```powershell
 Get-Content .\AzureSpringAppsServices.csv | ConvertFrom-Csv | select name | ForEach-Object {
@@ -138,7 +138,7 @@ Get-Content .\AzureSpringAppsServices.csv | ConvertFrom-Csv | select name | ForE
 
 ## Create a service and service group
 
-To automate the creation of services based on the *AzureSpringAppsServices.csv* file you created earlier, use the following example.
+To automate the creation of services based on the **AzureSpringAppsServices.csv** file you created earlier, use the following example.
 
 ```powershell
 # Define a function to create and submit a Palo Alto service creation request
@@ -258,7 +258,7 @@ Invoke-RestMethod -Method Post -Uri $url  -SkipCertificateCheck -Headers $paloAl
 
 ## Create a security rule
 
-Next, create a JSON file to contain a security rule. Name the file *SecurityRule.json* and add the following content. The names of the two zones `Trust` and `UnTrust` match the zone names described earlier in the [Configure Palo Alto](#configure-palo-alto) section. The `service/member` entry contains the name of the service group created in the previous steps.
+Next, create a JSON file to contain a security rule. Name the file **SecurityRule.json** and add the following content. The names of the two zones `Trust` and `UnTrust` match the zone names described earlier in the [Configure Palo Alto](#configure-palo-alto) section. The `service/member` entry contains the name of the service group created in the previous steps.
 
 ```json
 {
@@ -338,7 +338,7 @@ Invoke-WebRequest -Uri $url -Method Post -Headers $paloAltoHeaders -Body (Get-Co
 
 ## Create Azure Monitor addresses
 
-Next, use the *AzureMonitorAddresses.csv* file to define Address objects in Palo Alto. The following example code shows you how to automate this task.
+Next, use the **AzureMonitorAddresses.csv** file to define Address objects in Palo Alto. The following example code shows you how to automate this task.
 
 ```powershell
 Get-Content ./AzureMonitorAddresses.csv | ConvertFrom-Csv | ForEach-Object {

articles/spring-apps/basic-standard/how-to-custom-domain.md

@@ -72,7 +72,7 @@ If your certificate authority gives you multiple certificates in the certificate
 
 To do this task, open each certificate you received in a text editor.
 
-Create a file for the merged certificate, called *mergedcertificate.crt*. In a text editor, copy the content of each certificate into this file. The order of your certificates should follow the order in the certificate chain, beginning with your certificate and ending with the root certificate. It looks like the following example:
+Create a file for the merged certificate, called **mergedcertificate.crt**. In a text editor, copy the content of each certificate into this file. The order of your certificates should follow the order in the certificate chain, beginning with your certificate and ending with the root certificate. It looks like the following example:
 
 ```crt
 -----BEGIN CERTIFICATE-----
@@ -96,15 +96,15 @@ Create a file for the merged certificate, called *mergedcertificate.crt*. In a t
 
 Export your merged TLS/SSL certificate with the private key that your certificate request was generated with.
 
-If you generated your certificate request using OpenSSL, then you have created a private key file. To export your certificate to PFX, run the following command. Replace the placeholders *<private-key-file>* and *<merged-certificate-file>* with the paths to your private key and your merged certificate file.
+If you generated your certificate request using OpenSSL, then you have created a private key file. To export your certificate to PFX, run the following command. Replace the placeholders <private-key-file> and <merged-certificate-file> with the paths to your private key and your merged certificate file.
 
 ```bash
 openssl pkcs12 -export -out myserver.pfx -inkey <private-key-file> -in <merged-certificate-file>
 ```
 
 When prompted, define an export password. Use this password when uploading your TLS/SSL certificate to Azure Key Vault later.
 
-If you used IIS or *Certreq.exe* to generate your certificate request, install the certificate to your local machine, and then [export the certificate to PFX](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc754329(v=ws.11)).
+If you used IIS or **Certreq.exe** to generate your certificate request, install the certificate to your local machine, and then [export the certificate to PFX](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc754329(v=ws.11)).
 
 ### Save certificate in Key Vault
 

articles/spring-apps/basic-standard/how-to-custom-persistent-storage.md

@@ -170,36 +170,36 @@ Use the following best practices when you add your own persistent storage to Azu
 
 - In the Azure Storage Account, avoid regenerating the account key that you're using. The storage account contains two different keys. Use a step-by-step approach to ensure that the persistent storage remains available to applications during key regeneration.
 
-   For example, use the following steps to ensure that the persistent storage remains available if you used *key1* to bind a storage account to Azure Spring Apps.
+   For example, use the following steps to ensure that the persistent storage remains available if you used `key1` to bind a storage account to Azure Spring Apps.
 
-   1. Regenerate *key2*.
-   1. Update the account key of the storage resource to use the regenerated *key2*.
+   1. Regenerate `key2`.
+   1. Update the account key of the storage resource to use the regenerated `key2`.
    1. Restart the applications that mount the persistent storage from this storage resource. Use the `az spring storage list-persistent-storage` command to list all related applications.
-   1. Regenerate *key1*.
+   1. Regenerate `key1`.
 
 - If you delete an Azure Storage account or Azure file share, avoid possible errors by removing the corresponding storage resource or persistent storage in the applications.
 
-- If you'd like to write files to the same path for every individual application instance, but keep them in separate subdirectories from the perspective of the file share, you could use the *SubPath* option. Note that the *SubPath* option is incompatible with *Read only* because *SubPath* is used for writing new files and *Read only* is used for reading existing files.
+- If you'd like to write files to the same path for every individual application instance, but keep them in separate subdirectories from the perspective of the file share, you could use the `SubPath` option. Note that the `SubPath` option is incompatible with `Read only` because `SubPath` is used for writing new files and `Read only` is used for reading existing files.
 
 ## FAQ
 
 This section addresses frequently asked questions about using your own persistent storage with Azure Spring Apps.
 
 - If I have built-in persistent storage enabled, and then I enabled my own storage as extra persistent storage, is my data migrated into my Azure Storage account?
 
-   *No. But we're going to provide a document to help you do the migration yourself soon.*
+   No. But we're going to provide a document to help you do the migration yourself soon.*
 
 - What are the reserved mount paths?
 
-  *Azure Spring Apps reserves the following mount paths:*
+   Azure Spring Apps reserves the following mount paths:
 
-  - */tmp*
-  - */persistent*
-  - */secrets*
-  - */app-insights/agents*
-  - */etc/azure-spring-cloud/certs*
-  - */app-insights/agents/settings*
-  - */app-lifecycle/settings*
+  - **/tmp**
+  - **/persistent**
+  - **/secrets**
+  - **/app-insights/agents**
+  - **/etc/azure-spring-cloud/certs**
+  - **/app-insights/agents/settings**
+  - **/app-lifecycle/settings**
 
 - What are the available mount options?
 

articles/spring-apps/basic-standard/how-to-deploy-in-azure-virtual-network.md

@@ -53,7 +53,7 @@ The virtual network to which you deploy your Azure Spring Apps instance must mee
   * One for the service runtime.
   * One for your Spring applications.
   * There's a one-to-one relationship between these subnets and an Azure Spring Apps instance. Use a new subnet for each service instance you deploy. Each subnet can only include a single service instance.
-* Address space: CIDR blocks up to */28* for both the service runtime subnet and the Spring applications subnet.
+* Address space: CIDR blocks up to `/28` for both the service runtime subnet and the Spring applications subnet.
 * Route table: By default the subnets don't need existing route tables associated. You can [bring your own route table](#bring-your-own-route-table).
 
 Use the following steps to set up the virtual network to contain the Azure Spring Apps instance.