Small whitespace and Markdown fixes

Signed-off-by: Tom Wieczorek <[email protected]>

docs/architecture/adr-001-autopilot-oci-basic-auth-support.md

@@ -6,12 +6,12 @@ Registries are increasingly being used as generic artifact stores, expanding
 beyond their traditional role of hosting container images. To align with this
 trend, it is beneficial for Autopilot to support pulling artifacts directly
 from registries. Currently, Autopilot's capabilities are limited to downloading
-artifacts via the HTTP[S] protocols.
+artifacts via the HTTP\[S\] protocols.
 
 Enhancing Autopilot to pull artifacts directly from registries will streamline
 workflows and improve efficiency by allowing integration and deployment of
-diverse artifacts without relying solely on HTTP[S] endpoints. This update will
-enable Autopilot to handle registry-specific protocols and authentication
+diverse artifacts without relying solely on HTTP\[S\] endpoints. This update
+will enable Autopilot to handle registry-specific protocols and authentication
 mechanisms, aligning it with modern deployment practices.
 
 Currently, Autopilot does not support the retrieval of artifacts via the HTTP
@@ -66,10 +66,10 @@ type PlanResourceURL struct {
 
 `SecretRef` property is of type `SecretReference` as defined by
 `k8s.io/api/core/v1` package. The secret pointed by the provided `SecretRef`
-will be used for pulling artifacts using either HTTP[S] or OCI protocols and is
-expected to by of type `kubernetes.io/dockerconfigjson` if the protocol in use
-is `oci://` or of type `Opaque` if protocols `http://` or `https://` are used
-(see below for details on the Secret layout).
+will be used for pulling artifacts using either HTTP\[S\] or OCI protocols and
+is expected to by of type `kubernetes.io/dockerconfigjson` if the protocol in
+use is `oci://` or of type `Opaque` if protocols `http://` or `https://` are
+used (see below for details on the Secret layout).
 
 Example configuration for OCI:
 
@@ -133,7 +133,7 @@ behaviour in case of conflicting configurations:
 
 > In the case where the three properties are set (`username`, `password`, and
 > `authorization`) Autopilot will ignore `username` and `password`, i.e.
-> `authorization`  takes precedence over username and password.
+> `authorization` takes precedence over username and password.
 
 The `authorization` entry is used as is, its content is placed directly into
 the `Authorization` header. For example a secret like the following will make