Apply suggestions from code review

Co-authored-by: Stefaan Lippens <[email protected]>

Author: m-mohr

openapi.yaml

@@ -6802,7 +6802,7 @@ components:
            The Bearer token is an access token in [JWT](https://datatracker.ietf.org/doc/html/rfc7519) format
            as defined in RFC 7519. For openEO, it MUST include the issuer in the
            `iss` claim although being optional in RFC 7519.
-           If the concept of an issuer doesn not exist in an authentication method (e.g. in HTTP Basic),
+           If the concept of an issuer does not exist in an authentication method (e.g. in HTTP Basic),
            implementations could use the endpoint for Basic Authentication as the issuer, for example.
 
            openEO backend implementations MUST signal their support for JWT by listing the given
@@ -6824,12 +6824,12 @@ components:
              For OpenID Connect, the provider ID corresponds to the value
              specified for `id` for each provider in `GET /credentials/oidc`.
 
-           All servers must accept this method for backward compatibility
+           All openEO backends MUST accept this method for backward compatibility
            until version 2.0 of the specification.
 
            The access tokens provided by the identity provider do not include
            the prefix that includes the authentication method and provider ID.
-           The Bearer Token sent to the server MUST have the prefix, e.g. `basic//` for Basic authentication.
+           The Bearer Token sent to the openEO backend MUST have the prefix, e.g. `basic//` for Basic authentication.
            This means that the clients have to prepend the prefix.
         
         JWT and openEO tokens can be distinguished by the presence of a slash