Skip to content

Commit cf00952

Browse files
authored
Update fhir-service-autoscale.md
1 parent ef63d0b commit cf00952

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/healthcare-apis/fhir/fhir-service-autoscale.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.author: kesheth
1313

1414
Azure Health Data Services provides a managed service for persisting FHIR-compliant healthcare data and interacting with it securely through the API service endpoint.
1515

16-
Autoscaling is a capability to dynamically scale FHIR service based on the load reported. The FHIR service in Azure Health Data Services provides the built-in autoscaling capability and the process is automated. This capability provides elasticity and enables provisioning of additional instances for FHIR service customers on demand.
16+
Autoscaling is a capability to dynamically scale FHIR service based on the load reported. The FHIR service in Azure Health Data Services provides the built-in autoscaling capability and the process is automated. This capability provides elasticity and enables provisioning of more instances for FHIR service customers on demand.
1717

1818
The autoscaling feature for FHIR service is available in all regions where the FHIR service is supported.
1919
> [!NOTE]
@@ -39,9 +39,9 @@ To ensure the best possible outcome, we recommend customers to gradually increas
3939

4040
The autoscaling feature incurs no extra costs to customers.
4141

42-
### What should customers do in case of high volume of HTTP 429 errors?
42+
### What should customers do if there is high volume of HTTP 429 errors?
4343

44-
We recommend customers to gradually increase the request rate to see if brings reduction in HTTP 429 erros. For consisent 429 errors, we ask customer(s) to create a support ticket through Azure portal on issue observed. Support team will engage to understand scaling trigger needs.
44+
We recommend customers to gradually increase the request rate to see if brings reduction in HTTP 429 errors. For consistent 429 errors, we ask customer(s) to create a support ticket through Azure portal on issue observed. Support team will engage to understand scaling trigger needs.
4545

4646
## Next steps
4747

0 commit comments

Comments
 (0)