Merge pull request #90 from krancour/fence-fixes

docs: fix invalid console code fences
brigadecore · May 17, 2022 · 8f82a92 · 8f82a92
2 parents 9038496 + f0a1248
commit 8f82a92
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 7 deletions.
diff --git a/README.md b/README.md
@@ -118,7 +118,7 @@ spec:
 Assuming this file were named `project.yaml`, you can create the project like
 so:
 
-```console
+```shell
 $ brig project create --file project.yaml
 ```
 
@@ -131,7 +131,7 @@ definition.
 
 List the events for the `bitbucket-demo` project to confirm this:
 
-```console
+```shell
 $ brig event list --project bitbucket-demo
 ```
 

diff --git a/docs/INSTALLATION.md b/docs/INSTALLATION.md
@@ -55,13 +55,13 @@
 
 ## Install the Gateway
 
-> ⚠️&nbsp;&nbsp;be sure you are using
+> ⚠️&nbsp;&nbsp;Be sure you are using
 > [Helm 3.7.0](https://github.com/helm/helm/releases/tag/v3.7.0) or greater and
 > enable experimental OCI support:
 >
-> ```console
->  $ export HELM_EXPERIMENTAL_OCI=1
->  ```
+> ```shell
+> $ export HELM_EXPERIMENTAL_OCI=1
+> ```
 
 1. As this gateway requires some specific configuration to function properly,
    we'll first create a values file containing those settings. Use the following
@@ -116,7 +116,7 @@
 If you overrode defaults and set `service.type` to `LoadBalancer`, use this
 command to find the gateway's public IP address:
 
-```console
+```shell
 $ kubectl get svc brigade-bitbucket-gateway \
     --namespace brigade-bitbucket-gateway \
     --output jsonpath='{.status.loadBalancer.ingress[0].ip}'