fixup! Update standard to include DR (#352)

Signed-off-by: Hannes Baum <[email protected]>

Standards/scs-0001-v2-sovereign-cloud-standards.md

@@ -15,7 +15,7 @@ The [Sovereign Cloud Stack (SCS)](https://scs.community) provides standards
 for a range of cloud infrastructure types.
 It strives for interoperable and sovereign cloud stacks
 which can be deployed and used by a wide range of organizations and individuals.
-Wherever feasible, transparency and openness both in respect to the inner workings of the platforms 
+Wherever feasible, transparency and openness both in respect to the inner workings of the platform
 standardised by SCS, and the SCS organization itself are a paradigm we intend to live.
 
 ## Requirements
@@ -227,7 +227,7 @@ Once the document is deemed ready for production use, its `status` is changed to
 
 After stabilization, changes to the document which may render existing implementations non-conformant MUST NOT be made.
 
-If a breaking change to an existing SCS document is deemed necessary, a new document with 
+If a breaking change to an existing SCS document is deemed necessary, a new document with
 a new number shall be created and the old document SHOULD be deprecated.
 
 ### Deprecation phase (Deprecated)
@@ -300,7 +300,7 @@ The disadvantages of that approach are:
   and raises questions around which changes are acceptable to "archived" versions,
   if any.
 
-- It would require a clone of the SemVer spec, as that spec is highly specific toward software and does not fully 
+- It would require a clone of the SemVer spec, as that spec is highly specific toward software and does not fully
   (at least not in the standard-as-written) cover specifics of a standards organisation's use-cases.
 
 ## Acknowledgements