Install: Improve syntax/formatting after converting to MyST Markdown

Author: amotl

docs/install/_control-linux.md

@@ -3,7 +3,7 @@
 
 You can control the `crate` service with the `systemctl` utility program:
 
-```
+```shell
 sudo systemctl COMMAND crate
 ```
 
@@ -17,12 +17,12 @@ After the installation is finished, the `crate` service should be installed,
 but may not be configured to start automatically. Use the following command to
 start CrateDB:
 
-```
+```shell
 sudo systemctl start crate
 ```
 
 In order to make the service reboot-safe, invoke:
 
-```
+```shell
 sudo systemctl enable crate
 ```

docs/install/cloud/aws/aws-terraform-setup.md

@@ -1,6 +1,6 @@
 (aws-terraform-setup)=
 
-# Running CrateDB via Terraform
+# Deploy using Terraform
 
 In {ref}`ec2_setup`, we elaborated on how to leverage EC2's functionality to set
 up a CrateDB cluster. Here, we will explore how to automate this kind of setup.
@@ -50,7 +50,7 @@ The CrateDB Terraform configuration consists of a set of variables to customize
 your deployment. Create a new file `main.tf` with the following content and
 adjust variable values as needed:
 
-```
+```terraform
 module "cratedb-cluster" {
   source = "github.com/crate/crate-terraform.git/aws"
 

docs/install/cloud/aws/ec2-setup.md

@@ -1,9 +1,6 @@
-```{highlight} yaml
-```
-
 (ec2-setup)=
 
-# Running CrateDB on Amazon EC2
+# CrateDB on Amazon EC2
 
 ## Introduction
 
@@ -60,7 +57,7 @@ CrateDB binds to the loopback interface by default. To get EC2 discovery
 working, you need to update the {ref}`host <crate-reference:conf_hosts>`
 setting, in order to bind to and publish the site-local address:
 
-```
+```yaml
 network.host: _site_
 ```
 
@@ -134,7 +131,7 @@ security group then, you can easily filter instances by that group.
 For example, when you launch your instances with the security group
 `sg-crate-demo`, your CrateDB setting would be:
 
-```
+```yaml
 discovery.ec2.groups: sg-crate-demo
 ```
 
@@ -181,7 +178,7 @@ This way, any number of tags can be used for filtering, using the
 Filtering by tags can help when you want to launch several CrateDB clusters
 within the same security group, e.g:
 
-```
+```yaml
 discovery.ec2:
     groups: sg-crate-demo
     tag.env: production
@@ -198,7 +195,7 @@ you have several clusters for the same tenant in different availability zones
 same security group (e.g. `sg-crate-demo`) and filter the instances used for
 discovery by availability zone:
 
-```
+```yaml
 discovery.ec2:
     groups: sg-crate-demo
     availability_zones: us-west-1

docs/install/cloud/aws/s3-setup.md

@@ -1,6 +1,3 @@
-```{highlight} yaml
-```
-
 (s3-setup)=
 
 # Using Amazon S3 as a snapshot repository
@@ -15,7 +12,7 @@ Support for *Snapshot* and *Restore* to the [Amazon S3] service is enabled by
 default in CrateDB. If you need to explicitly turn it off, disable the cloud
 setting in the `crate.yml` file:
 
-```
+```yaml
 cloud.enabled: false
 ```
 

docs/install/cloud/azure/terraform.md

@@ -1,6 +1,6 @@
 (azure-terraform-setup)=
 
-# Running CrateDB via Terraform
+# Deploy using Terraform
 
 In {ref}`azure_vm_setup`, we elaborated on how to leverage Azure's functionality to
 set up a CrateDB cluster. Here, we will explore how to automate this kind of
@@ -51,7 +51,7 @@ The CrateDB Terraform configuration consists of a set of variables to customize
 your deployment. Create a new file `main.tf` with the following content and
 adjust variable values as needed:
 
-```
+```terraform
 module "cratedb-cluster" {
   source = "github.com/crate/crate-terraform.git/azure"
 

docs/install/cloud/azure/vm.md

@@ -1,6 +1,6 @@
 (azure-vm-setup)=
 
-# Running CrateDB on Azure VMs
+# CrateDB on Azure VMs
 
 Getting CrateDB working on Azure with Linux or Windows is a simple process. You
 can use Azure's management console or CLI interface ([Learn how to install

docs/install/cloud/index.md

@@ -1,6 +1,6 @@
 (install-cloud)=
 
-# Cloud Hosting
+# Cloud hosting
 
 CrateDB provides packages and executables that will work on any operating
 system capable of running Java.

docs/install/configure.md

@@ -32,7 +32,7 @@ working directory.
 
 Here is an example:
 
-```
+```shell
 # Configure heap size (defaults to 256m min, 1g max).
 CRATE_HEAP_SIZE=2g
 

docs/install/container/docker.md

@@ -1,6 +1,3 @@
-```{highlight} sh
-```
-
 (cratedb-docker)=
 
 # Run CrateDB on Docker
@@ -35,7 +32,7 @@ with no vote.
 
 To create the [user-defined network], run the command:
 
-```
+```shell
 sh$ docker network create crate
 ```
 
@@ -120,7 +117,7 @@ f79116373877        crate               "/docker-entrypoin..."   16 seconds ago
 
 You can have a look at the container's logs in tail mode like this:
 
-```text
+```shell
 sh$ docker logs -f crate01
 ```
 
@@ -139,7 +136,7 @@ page that lists a single node.
 
 Now add the second node, `crate02`, to the cluster:
 
-```
+```shell
 sh$ docker run --rm -d \
       --name=crate02 \
       --net=crate \
@@ -169,7 +166,7 @@ should see two nodes.
 
 You can now add `crate03` like this:
 
-```
+```shell
 sh$ docker run --rm -d \
       --name=crate03 \
       --net=crate -p 4203:4200  \
@@ -213,7 +210,7 @@ If the limit cannot be adjusted on the host system, the memory map limit check
 can be bypassed by passing the `-Cnode.store.allow_mmap=false` option to
 the `crate` command:
 
-```
+```shell
 sh$ docker run -d --name=crate01 \
       --net=crate -p 4201:4200 --env CRATE_HEAP_SIZE=1g \
       crate -Cnetwork.host=_site_ \
@@ -227,7 +224,7 @@ This will result in degraded performance.
 You can also start a single node without any {ref}`bootstrap checks
 <bootstrap-checks>` by passing the `-Cdiscovery.type=single-node` option:
 
-```
+```shell
 sh$ docker run -d --name=crate01 \
       --net=crate -p 4201:4200 \
       --env CRATE_HEAP_SIZE=1g \
@@ -255,7 +252,7 @@ If you wanted to run `crash` inside a user-defined network called `crate`
 and connect to three hosts named `crate01`, `crate02`, and `crate03`
 (i.e. the example covered in the [Creating a Cluster] section) you could run:
 
-```
+```shell
 $ docker run --rm -ti \
     --net=crate crate \
     crash --hosts crate01 crate02 crate03
@@ -370,7 +367,7 @@ per host machine.
 If you are running one container per machine, you can map the container ports
 to the host ports so that the host acts like a native installation. For example:
 
-```
+```shell
 $ docker run -d -p 4200:4200 -p 4300:4300 -p 5432:5432 --env CRATE_HEAP_SIZE=1g crate \
     crate -Cnetwork.host=_site_
 ```
@@ -382,7 +379,7 @@ and go, and any data inside them is lost when the container is removed. For
 this reason, you should mount a persistent `data` directory on your host
 machine to the `/data` directory inside the container:
 
-```
+```shell
 $ docker run -d -v /srv/crate/data:/data --env CRATE_HEAP_SIZE=1g crate \
     crate -Cnetwork.host=_site_
 ```
@@ -401,7 +398,7 @@ removed.
 
 Here is an example of how you could mount the `crate.yml` config file:
 
-```
+```shell
 $ docker run -d \
     -v /srv/crate/config/crate.yml:/crate/config/crate.yml \
     --env CRATE_HEAP_SIZE=1g crate \
@@ -470,7 +467,7 @@ If you want the container to use a maximum of 1.5 CPUs, a maximum of 2 GB
 memory, with a heap size of 1 GB, you could configure everything at once. For
 example:
 
-```
+```shell
 $ docker run -d \
     --cpus 1.5 \
     --memory 1g \

docs/install/container/index.md

@@ -1,12 +1,10 @@
 (install-container)=
 
-# Container Setup
+# Container setup
 
-```{eval-rst}
-.. div:: sd-text-muted
-
-    Install CrateDB in container environments.
-```
+:::{div} sd-text-muted
+Install CrateDB in container environments.
+:::
 
 CrateDB is ideal for containerized environments, creating and scaling a cluster
 takes minutes and your valuable data is always in sync and available.