Merge pull request #2558 from OctopusDeploy/formatting-fix

Fixing formatting issues

src/pages/docs/kubernetes/steps/helm.md

@@ -192,9 +192,13 @@ To ensure a smooth deployment experience, we recommend setting a larger Octopus
 
 :::div{.hint}
 **Step updates**
+
 **2024.1:**
+
 - `Upgrade a Helm Chart` was renamed to `Deploy a Helm chart`.
 - Support was added for Helm charts stored in Git repositories. You can learn more in [this blog post](https://octopus.com/blog/git-resources-in-deployments).
+
 **2023.3.4127**
+
 - Support was added for Helm repositories stored in OCI-based registries.
 :::

src/pages/docs/kubernetes/steps/kubernetes-ingress.md

@@ -79,6 +79,8 @@ When there are no matching ingress rules, traffic can be sent to the service con
 
 :::div{.hint}
 **Step updates**
+
 **2024.1:**
+
 - `Deploy Kubernetes ingress resource` was renamed to `Configure and apply a Kubernetes Ingress`.
 :::

src/pages/docs/kubernetes/steps/kubernetes-resources.md

@@ -1053,6 +1053,8 @@ For example, to change the name assigned to the ConfigMap resource to include th
 
 :::div{.hint}
 **Step updates**
+
 **2024.1:**
+
 - `Deploy Kubernetes containers` was renamed to `Configure and apply Kubernetes resources`.
 :::

src/pages/docs/kubernetes/steps/kubernetes-service.md

@@ -79,6 +79,8 @@ There are some advanced use cases where creating a Service resource without sele
 
 :::div{.hint}
 **Step updates**
+
 **2024.1:**
+
 - `Deploy Kubernetes service resource` was renamed to `Configure and apply a Kubernetes Service`.
 :::

src/pages/docs/kubernetes/steps/kustomize.mdx

@@ -91,7 +91,9 @@ The "`#{Octopus.Action.Package[nginx].PackageVersion}`" Octostache expression wi
 
 :::div{.hint}
 **Step updates**
+
 **2024.1:**
+
 - `Kustomize` was renamed to `Deploy with Kustomize`.
 - If you store your project configuration in a Git repository using the [Configuration as code feature](/docs/projects/version-control), you can source your Kustomize files from the same Git repository as your deployment process by selecting Project as the Git repository source. When creating a Release, the commit hash used for your deployment process will also be used to source the Kustomize files. You can learn more in [this blog post](https://octopus.com/blog/git-resources-in-deployments).
 :::

src/pages/docs/kubernetes/steps/yaml.md

@@ -113,9 +113,13 @@ There are a few different ways to take advantage of this feature:
 
 :::div{.hint}
 **Step updates**
+
 **2024.1:**
+
 - `Deploy Raw Kubernetes YAML` was renamed to `Deploy Kubernetes YAML`.
 - If you store your project configuration in a Git repository using the [Configuration as code feature](/docs/projects/version-control), you can source your YAML from the same Git repository as your deployment process by selecting Project as the Git repository source. When creating a Release, the commit hash used for your deployment process will also be used to source the YAML files. You can learn more in [this blog post](https://octopus.com/blog/git-resources-in-deployments).
+
 **2023.3:**
+
 - Sourcing from Git Repositories was added. You can learn more in [this blog post](https://octopus.com/blog/manifests-from-git).
 :::