Skip to content

Commit db9b4bd

Browse files
committed
Acrolinx fixes
1 parent 658a6e8 commit db9b4bd

File tree

5 files changed

+14
-16
lines changed

5 files changed

+14
-16
lines changed

articles/spring-apps/faq.md

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ Azure Spring Apps is a regional service. All customer data in Azure Spring Apps
5757

5858
Azure Spring Apps has the following known limitations:
5959

60-
* `spring.application.name` will be overridden by the application name that's used to create each application.
60+
* `spring.application.name` is overridden by the application name that's used to create each application.
6161
* `server.port` defaults to port 1025. If any other value is applied, it's overridden, so don't specify a server port in your code.
6262
* The Azure portal, Azure Resource Manager templates, and Terraform don't support uploading application packages. You can upload application packages by deploying the application using the Azure CLI, Azure DevOps, Maven Plugin for Azure Spring Apps, Azure Toolkit for IntelliJ, and the Visual Studio Code extension for Azure Spring Apps.
6363

@@ -236,22 +236,20 @@ For more information, see [Migrate Spring applications to Azure Spring Apps](/az
236236

237237
### How long is .NET Core 3.1 supported?
238238

239-
Until Dec 3, 2022. See [.NET Core Support Policy](https://dotnet.microsoft.com/platform/support/policy/dotnet-core).
239+
Until December 3, 2022. See [.NET Core Support Policy](https://dotnet.microsoft.com/platform/support/policy/dotnet-core).
240240
::: zone-end
241241

242242
## Troubleshooting
243243

244244
### What are the impacts of service registry rarely unavailable?
245245

246-
In some rarely happened scenario, you may see some errors like the following one from your application logs:
246+
In some rare scenarios, you may see errors like the following from your application logs:
247247

248248
```output
249249
RetryableEurekaHttpClient: Request execution failure with status code 401; retrying on another server if available
250250
```
251251

252-
This issue is introduced by the Spring framework at a low rate due to network instability or other network issues.
253-
254-
There should be no impacts to the user experience. The Eureka client has both heartbeat and retry policy to take care of this problem. You could consider it as one transient error and skip it safely.
252+
The Spring framework raises this issue at a low rate due to network instability or other network issues. There should be no impacts to the user experience. The Eureka client has both heartbeat and retry policy to take care of this problem. You can consider it a transient error and skip it safely.
255253

256254
## Next steps
257255

articles/spring-apps/how-to-staging-environment.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -172,7 +172,7 @@ If you visit your public-facing app gateway at this point, you should see the ol
172172

173173
## Set the green deployment as the production environment
174174

175-
1. After you have verified your change in your staging environment, you can push it to production. On the **Apps** > **Deployments** page, select the application currently in **Production**.
175+
1. After you've verified your change in your staging environment, you can push it to production. On the **Apps** > **Deployments** page, select the application currently in **Production**.
176176

177177
1. Select the ellipsis after **Registration status** of the green deployment, and then select **Set as production**.
178178

@@ -183,7 +183,7 @@ If you visit your public-facing app gateway at this point, you should see the ol
183183
:::image type="content" source="media/how-to-staging-environment/new-production-deployment.png" lightbox="media/how-to-staging-environment/new-production-deployment.png" alt-text="Screenshot that shows the URL of the app now in production.":::
184184

185185
>[!NOTE]
186-
> After you have set the green deployment as the production environment, the previous deployment becomes the staging deployment.
186+
> After you've set the green deployment as the production environment, the previous deployment becomes the staging deployment.
187187
188188
## Modify the staging deployment
189189

articles/spring-apps/quickstart-deploy-apps.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ This quickstart explains how to build and deploy Spring applications to Azure Sp
2929

3030
## Download the sample app
3131

32-
Use the following steps to download the sample app. If you have been using the Azure Cloud Shell, switch to a local command prompt.
32+
Use the following steps to download the sample app. If you've been using the Azure Cloud Shell, switch to a local command prompt.
3333

3434
1. Create a new folder and clone the sample app repository.
3535

@@ -55,13 +55,13 @@ Use the following steps to download the sample app. If you have been using the A
5555

5656
Use the following steps to deploy the PlanetWeatherProvider project.
5757

58-
1. Create an app for the PlanetWeatherProvider project in your Azure Spring Apps instance.
58+
1. Create an app for the `PlanetWeatherProvider` project in your Azure Spring Apps instance.
5959

6060
```azurecli
6161
az spring app create --name planet-weather-provider --runtime-version NetCore_31
6262
```
6363

64-
To enable automatic service registration, you have given the app the same name as the value of `spring.application.name` in the project's *appsettings.json* file:
64+
To enable automatic service registration, you've given the app the same name as the value of `spring.application.name` in the project's *appsettings.json* file:
6565

6666
```json
6767
"spring": {
@@ -333,13 +333,13 @@ Compiling the project takes 5-10 minutes. When the project is compiled, you shou
333333

334334
The following steps show you how to generate configurations and deploy to Azure Spring Apps.
335335

336-
1. Generate configurations by running the following command in the root folder of Pet Clinic containing the parent POM. If you have already signed-in with Azure CLI, the command automatically picks up the credentials. Otherwise, it signs you in with prompt instructions. For more information, see our [wiki page](https://github.com/microsoft/azure-maven-plugins/wiki/Authentication).
336+
1. Generate configurations by running the following command in the root folder of Pet Clinic containing the parent POM. If you've already signed-in with Azure CLI, the command automatically picks up the credentials. Otherwise, it signs you in with prompt instructions. For more information, see our [wiki page](https://github.com/microsoft/azure-maven-plugins/wiki/Authentication).
337337

338338
```bash
339339
mvn com.microsoft.azure:azure-spring-apps-maven-plugin:1.10.0:config
340340
```
341341

342-
You'll be asked to select:
342+
You're asked to select:
343343

344344
- **Modules:** Select `api-gateway` and `customers-service`.
345345
- **Subscription:** The subscription you used to create an Azure Spring Apps instance.

articles/spring-apps/quickstart-sample-app-introduction.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -85,7 +85,7 @@ The following diagram shows the architecture of the PetClinic application.
8585

8686
## Functional services to be deployed
8787

88-
PetClinic is decomposed into 4 core Spring apps. All of them are independently deployable applications organized by business domains.
88+
PetClinic is decomposed into four core Spring apps. All of them are independently deployable applications organized by business domains.
8989

9090
* **Customers service**: Contains general user input logic and validation including pets and owners information (Name, Address, City, Telephone).
9191
* **Visits service**: Stores and shows visits information for each pet's comments.

articles/spring-apps/toc.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -315,9 +315,9 @@ items:
315315
href: how-to-enable-redundancy-and-disaster-recovery.md
316316
- name: Troubleshoot
317317
items:
318-
- name: Self diagnose and solve problems
318+
- name: Self-diagnose and solve problems
319319
href: how-to-self-diagnose-solve.md
320-
- name: Self diagnose running in virtual networks
320+
- name: Self-diagnose running in virtual networks
321321
href: how-to-self-diagnose-running-in-vnet.md
322322
- name: Troubleshoot common issues
323323
href: troubleshoot.md

0 commit comments

Comments
 (0)