chore: small markdown tweaks

Author: SaphMB

docs/main/03-reference/13-destinations/01-destinations.md

@@ -10,11 +10,12 @@ a system that Kratix can write documents to. These documents are then
 reconciled by an external tool.
 
 Some example use cases:
+
 - [Kubernetes cluster](https://kubernetes.io/): Kratix will scheduled documents (Kubernetes manifests) to
   the Destination, and then a GitOps tool running on the Kubernetes cluster,
   such as Flux or ArgoCD with pull down the documents and deploy them. See our
   [GitOps Agent documentation](/category/installing-gitops-agent) for more information.
-- [Terraform](https://www.terraform.io/): There are many toolings that exist to trigger Terraform applys
+- [Terraform](https://www.terraform.io/): There are many toolings that exist to trigger a `teraform apply`
   when a new Terraform file is committed to a Git repository. For example
   [Terraform
   Enterprise](https://www.hashicorp.com/resources/gitops-and-terraform-enterprise-a-match-made-in-heaven-at-state-farm)
@@ -25,8 +26,8 @@ Some example use cases:
   filled from a Git
   repository](https://backstage.io/docs/integrations/github/discovery).
 
-
 Below is the full Spec for the Destination CRD:
+
 ```yaml
 apiVersion: platform.kratix.io/v1alpha1
 kind: Destination
@@ -79,7 +80,7 @@ one for `resources`, one for `dependencies`. The path within the `State Store` f
 
 For `dependencies`:
 
-```
+```yaml
 statestore.Spec.Path/
     destination.Spec.Path/
         destination.Name/
@@ -89,7 +90,7 @@ statestore.Spec.Path/
 
 For `resources`:
 
-```
+```yaml
 statestore.Spec.Path/
     destination.Spec.Path/
         destination.Name/
@@ -101,7 +102,7 @@ statestore.Spec.Path/
 
 For example installing and requesting from a Promise that provides `Redis` as a service you would get:
 
-```
+```bash
 worker-cluster/dependencies/redis/static/dependencies.yaml
 worker-cluster/resources/default/redis/my-request/redis.yaml
 ```

docs/main/03-reference/15-resources/04-status.md

@@ -150,6 +150,7 @@ iam:
 ```
 
 The end status would be:
+
 ```yaml
 status:
   conditions:
@@ -209,7 +210,7 @@ Configure workflow has completed. `kubectl` also has built-in support for waitin
 condition to be met. For example, after requesting a Resource, a user can run the
 following to have the CLI wait for the Workflow to be completed:
 
-```
+```bash
 kubectl wait redis/example --for=condition=ConfigureWorkflowCompleted --timeout=60s
 ```
 

docs/ske/60-ske-cli/01-reference/04_ske-upgrade.md

@@ -3,7 +3,8 @@
 Upgrade SKE to the next minor at the latest patch
 
 ## Description
-```
+
+```bash
  > ske upgrade
 
 Upgrading SKE from v0.9.0 to v0.10.0...
@@ -29,21 +30,20 @@ Upgrade successful!
 ```
 
 ## Usage
-```
+
+```bash
 ske upgrade [--context] [flags]
 ```
 
-
 ## Flags
-```
+
+```bash
       --dry-run            Dry run the upgrade
   -h, --help               help for upgrade
       --skip-all-checks    Skipping all pre- and post-upgrade checks; use with caution
       --timeout duration   Timeout for the upgrade (default 5m0s)
 ```
 
-
 ## See Also
 
 * [ske](/ske/ske-cli/reference/ske): The ske CLI
-