Skip to content

Commit 1d2ca96

Browse files
depressiveRobotmbuechse
authored andcommitted
fix yet another typo
Signed-off-by: Marvin Frommhold <[email protected]>
1 parent 82ac396 commit 1d2ca96

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

Standards/scs-0121-w1-Availability-Zones-Standard.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ supplements:
1010

1111
The standard will not preclude small deployments and edge deployments, that both will not meet the requirement for being divided into multiple Availability Zones.
1212
Thus multiple Availability Zones are not always present.
13-
Somtimes there can just be a single Availability Zone.
13+
Sometimes there can just be a single Availability Zone.
1414
Because of that, there will be no automated tests to search for AZs.
1515

1616
## Required Documentation
@@ -25,7 +25,7 @@ For each deployment, that uses more than a single Availability Zone, the CSP has
2525
5. The redundancy in core routers within each AZ MUST be documented.
2626

2727
After the initial setup, these requirements typically do not change at all (like the fire zones) or are very unlikely to change (like redundant internet connection).
28-
Because of this, documentation needs to only be provided in the following cases:
28+
Because of this, documentation needs to be provided only in the following cases:
2929

3030
1. When a new deployment with multiple AZs should be tested for compliance initially.
3131
2. When there are physical changes in a deployment which already provided the documentation: the changes need to be documented and provided as soon as possible.

0 commit comments

Comments
 (0)