Skip to content

Commit 377f369

Browse files
fix yet another typo
Signed-off-by: Marvin Frommhold <depressiveRobot@users.noreply.github.com>
1 parent 7bb5560 commit 377f369

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

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

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

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

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

2929
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).
30-
Because of this, documentation needs to only be provided in the following cases:
30+
Because of this, documentation needs to be provided only in the following cases:
3131

3232
1. When a new deployment with multiple AZs should be tested for compliance initially.
3333
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)