make vale happy

vshn · Dec 6, 2024 · b21fc8c · b21fc8c
1 parent e3f3fc8
commit b21fc8c
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/modules/ROOT/pages/reference/arch-control-plane.adoc b/docs/modules/ROOT/pages/reference/arch-control-plane.adoc
@@ -152,7 +152,7 @@ The Compositions define the exact characteristic of a service, exposing all the
 The service catalog is defined on the CCP by adding the necessary configurations via a Project Syn Commodore Component.
 The XRD for each service on the CCP is exactly the same as the one on the CSPCP, the differentiation lies in the https://docs.crossplane.io/latest/concepts/composite-resources/#composition-selection[`spec.compositionRef`^].
 
-Depending on which Composition is selected, the service is instantiated at a different place (e.g. service provider zone).
+Depending on which Composition is selected, the service is instantiated at a different place (for example service provider zone).
 This allows for true portability, the API spec per service is the same, no matter if the service is provisioned on the CCP, on a CSPCP or directly in a cluster.
 
 The Composition on the CCP wraps the Claim in an `Object` type from https://github.com/crossplane-contrib/provider-kubernetes[provider-kubernetes^].

diff --git a/docs/modules/ROOT/pages/reference/exoscale-osbapi.adoc b/docs/modules/ROOT/pages/reference/exoscale-osbapi.adoc
@@ -172,7 +172,7 @@ The origin `spec.origin` is set to "Exoscale" (hardcoded in the OSB API service)
 Invitation::
 When the Organization is created the first time, an https://kb.vshn.ch/appuio-cloud/references/architecture/control-api-invitation.html[`Invitation`^] object is created, sending an invitation to the user in the field `parameters.users[0].email` from the OSB API.
 
-To keep track of provisioning requests and enabling access to services, we store an `ProvidedService` (see xref:reference/arch-control-plane.adoc[]) object in the organization namespace, containing all the details of the provisioning call, including `.status` which stores the details what happened (e.g. organization created or already existed, Exoscale API informed, ...)
+To keep track of provisioning requests and enabling access to services, we store an `ProvidedService` (see xref:reference/arch-control-plane.adoc[]) object in the organization namespace, containing all the details of the provisioning call, including `.status` which stores the details what happened (for example organization created or already existed, Exoscale API informed, ...)
 
 === Suspension