Skip to content

Commit da6f75b

Browse files
author
Jill Grant
authored
Update using.md
Acrolinx fix
1 parent 325a499 commit da6f75b

File tree

1 file changed

+1
-1
lines changed
  • articles/app-service/environment

1 file changed

+1
-1
lines changed

articles/app-service/environment/using.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ When you scale an App Service plan, the needed infrastructure is added automatic
4949

5050
A scale operation on one size and operating system won't affect scaling of the other combinations of size and operating system. For example, if you are scaling a Windows I2v2 App Service plan, a scale operation to a Windows I3v2 App Service plan starts immediately. Scaling normally takes less than 15 minutes but can take up to 45 minutes.
5151

52-
In a multi-tenant App Service, scaling is immediate, because a pool of shared resources is readily available to support it. App Service Environment is a single-tenant service, so there's no shared buffer, and resources are allocated based on need.
52+
In a multitenant App Service, scaling is immediate, because a pool of shared resources is readily available to support it. App Service Environment is a single-tenant service, so there's no shared buffer, and resources are allocated based on need.
5353

5454
## App access
5555

0 commit comments

Comments
 (0)