Install: Implement suggestions by CodeRabbit

Author: amotl

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

@@ -26,9 +26,9 @@ instances.
 ### Authentication
 
 It is recommended to restrict the permissions of CrateDB on S3 to only the
-required extent. First, an IAM role is required. This [AWS guide] gives a
-short description of how to create a policy either using the CLI or the AWS
-Management Console. Further, access of the snapshot to the S3 bucket needs to
+required extent. First, an IAM role is required. This [AWS IAM policy guide]
+explains how to create a policy by using the CLI or the AWS Management Console.
+Further, access of the snapshot to the S3 bucket needs to
 be restricted. An example policy file granting anybody access to a bucket
 called `snaps.example.com` is attached below:
 
@@ -92,7 +92,7 @@ within the policy:
 ```
 
 [amazon s3]: https://aws.amazon.com/s3/
-[aws guide]: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-roles-for-amazon-ec2.html
+[AWS IAM policy guide]: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-roles-for-amazon-ec2.html
 [aws policy examples]: https://docs.aws.amazon.com/AmazonS3/latest/dev/example-bucket-policies.html
 [aws principals]: https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_principal.html
 [iam roles]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html

docs/install/container/docker.md

@@ -84,25 +84,26 @@ Breaking the command down:
 - Defines the environment variable {ref}`CRATE_HEAP_SIZE <crate-reference:conf-env-heap-size>`,
   which is used by CrateDB to allocate 1 GB for its heap memory.
 - Runs the command `crate` inside the container with parameters:
-    - `network.host`: The `_site_` value results in the binding of the
-      CrateDB process to a site-local IP address.
-    - `node.name`: Defines the node's name as `crate01` (used by
-      master election).
-    - `discovery.seed_hosts`: This parameter lists the other hosts in the
-      cluster. The format is a comma-separated list of `host:port` entries,
-      where port defaults to setting `transport.tcp.port`. Each node must
-      contain the name of all the other hosts in this list. Notice also that
-      any node in the cluster might be started at any time, and this will
-      create connection exceptions in the log files, however all nodes will
-      eventually be running and interconnected.
-    - `cluster.initial_master_nodes`: Defines the list of master-eligible
-      node names which will participate in the vote of the first master
-      (first bootstrap). If this parameter is not defined, then it is expected
-      that the node will join an already formed cluster. This parameter is only
-      relevant for the first election.
-    - `gateway.expected_data_nodes` and `gateway.recover_after_data_nodes`:
-      Specifies how many nodes you expect in the cluster and how many nodes must
-      be discovered before the cluster state is recovered.
+
+  - `network.host`: The `_site_` value results in the binding of the
+    CrateDB process to a site-local IP address.
+  - `node.name`: Defines the node's name as `crate01` (used by
+    master election).
+  - `discovery.seed_hosts`: This parameter lists the other hosts in the
+    cluster. The format is a comma-separated list of `host:port` entries,
+    where port defaults to setting `transport.tcp.port`. Each node must
+    contain the name of all the other hosts in this list. Notice also that
+    any node in the cluster might be started at any time, and this will
+    create connection exceptions in the log files, however all nodes will
+    eventually be running and interconnected.
+  - `cluster.initial_master_nodes`: Defines the list of master-eligible
+    node names which will participate in the vote of the first master
+    (first bootstrap). If this parameter is not defined, then it is expected
+    that the node will join an already formed cluster. This parameter is only
+    relevant for the first election.
+  - `gateway.expected_data_nodes` and `gateway.recover_after_data_nodes`:
+    Specifies how many nodes you expect in the cluster and how many nodes must
+    be discovered before the cluster state is recovered.
 
 :::{NOTE}
 If this command aborts with an error, consult the
@@ -269,7 +270,7 @@ Docker's Compose tool allows developers to define and run multi-container
 Docker applications that can be started with a single `docker-compose up`
 command.
 
-Read about Docker Compose specifics [here](https://docs.docker.com/compose/).
+Read about Docker Compose specifics in the [Docker Compose documentation](https://docs.docker.com/compose/).
 
 You can define the services that make up your app in a `docker-compose.yml`
 file. To recreate the three-node cluster in the previous example, you can

docs/install/container/kubernetes/kubernetes.md

@@ -273,7 +273,7 @@ spec:
   volumeClaimTemplates:
     # Use persistent storage.
     - metadata:
-        name: data
+        name: cratedb-data
       spec:
         accessModes:
         - ReadWriteOnce