Skip to content

Commit ae276ae

Browse files
garloffmbuechse
andcommitted
Apply suggestions from code review
The obvious ones from @mbuechse Co-authored-by: Matthias Büchse <[email protected]> Signed-off-by: Kurt Garloff <[email protected]>
1 parent 709b241 commit ae276ae

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

Standards/scs-0004-w1-achieving-certification-implementation.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "Implementtaion hints for achieveing SCS-compatible certification"
2+
title: "Implementation hints for achieving SCS-compatible certification"
33
type: Supplement
44
track: Global
55
status: Draft
@@ -10,7 +10,7 @@ supplements:
1010
## Process overview
1111

1212
The *SCS-compatible* Certification for Operators is a technical certification:
13-
The Operator needs to fulfill technical requirements, such as providing certain
13+
The operator needs to fulfill technical requirements, such as providing certain
1414
APIs and guaranteeing certain platform behavior in order to be certifiable.
1515

1616
These requirements are meant to provide guarantees to their customers, allowing
@@ -41,8 +41,8 @@ The best approach to get your cloud into compliance is by installing the
4141
test suite locally. Have a look at the
4242
[blog article](https://scs.community/blog/2024/10/14/cert-adapt-example/).
4343

44-
A description how *SCS-compatible IaaS* compliance can be achieved on environments that use different
45-
OpenStack implementations is written up in a blog article
44+
A description of how *SCS-compatible IaaS* compliance can be achieved on OpenStack environments that
45+
do not use the SCS reference implementation is written up in the blog article
4646
[Cost of making an OpenStack Cluster SCS compliant](https://scs.community/2024/05/13/cost-of-making-an-openstack-cluster-scs-compliant/).
4747

4848
## Declarations

0 commit comments

Comments
 (0)