Spruce up docs

Author: siggisim

docs/cloud.md

@@ -1,12 +1,12 @@
 <!--
 {
-  "name": "Cloud",
+  "name": "Cloud Quickstart",
   "category": "5eeba6a6c5230e48eea60f18",
   "priority": 800
 }
 -->
 
-# BuildBuddy Cloud
+# Cloud Quickstart
 
 [Cloud BuildBuddy](https://app.buildbuddy.io/) is a fully managed SaaS solution for Enterprise Bazel features. It provides a results store & UI, remote build caching, remote build execution, and more.
 
@@ -38,8 +38,7 @@ INFO: Streaming build results to: https://app.buildbuddy.io/invocation/24a37b8f-
 INFO: Build completed successfully, 1 total action
 ```
 
-You can ⌘ + double-click on these urls to quickly view the invocation's details. 
-
+You can ⌘ + double-click on these urls to quickly view the invocation's details.
 
 ## Authentication
 

docs/config-api.md

@@ -7,23 +7,24 @@
 -->
 
 # API Configuration
+
 The API is only configurable in the [Enterprise version](enterprise.md) of BuildBuddy.
 
 ## Section
 
-```api:``` The API section enables the BuildBuddy API over both gRPC(s) and REST HTTP(s). **Optional**
+`api:` The API section enables the BuildBuddy API over both gRPC(s) and REST HTTP(s). **Optional**
 
 ## Options
 
 **Optional**
 
-* ```enable_api:``` Whether or not to enable the BuildBuddy API.
+- `enable_api:` Whether or not to enable the BuildBuddy API.
 
-* ```api_key:``` The default API key to use for on-prem enterprise deploys with a single organization/group.
+- `api_key:` The default API key to use for on-prem enterprise deploys with a single organization/group.
 
 ## Example section
 
 ```
 api:
   enable_api: true
-```
+```

docs/config-app.md

@@ -5,28 +5,28 @@
   "priority": 800
 }
 -->
-# App Configuration
 
+# App Configuration
 
 ## Section
 
-```app:``` The app section contains app-level options. **Required**
+`app:` The app section contains app-level options. **Required**
 
 ## Options
 
 **Required**
 
-* ```build_buddy_url```  Configures the external URL where your BuildBuddy instance can be found. (Does not actually change the server address or port, see [flags docs](config-flags.md) for information on how to configure ports)
+- `build_buddy_url` Configures the external URL where your BuildBuddy instance can be found. (Does not actually change the server address or port, see [flags docs](config-flags.md) for information on how to configure ports)
 
 **Optional**
 
-* ```events_api_url```  Overrides the default build event protocol gRPC address shown by BuildBuddy on the configuration screen. (Does not actually change the server address)
+- `events_api_url` Overrides the default build event protocol gRPC address shown by BuildBuddy on the configuration screen. (Does not actually change the server address)
 
-* ```cache_api_url``` Overrides the default remote cache protocol gRPC address shown by BuildBuddy on the configuration screen. (Does not actually change the server address)
+- `cache_api_url` Overrides the default remote cache protocol gRPC address shown by BuildBuddy on the configuration screen. (Does not actually change the server address)
 
-* ```remote_execution_api_url``` Overrides the default remote execution protocol gRPC address shown by BuildBuddy on the configuration screen. (Does not actually change the server address)
+- `remote_execution_api_url` Overrides the default remote execution protocol gRPC address shown by BuildBuddy on the configuration screen. (Does not actually change the server address)
 
-* ```default_to_dense_mode``` Enables Dense UI mode by default.
+- `default_to_dense_mode` Enables Dense UI mode by default.
 
 ## Example section
 

docs/config-auth.md

@@ -5,21 +5,23 @@
   "priority": 300
 }
 -->
+
 # Auth Configuration
 
 Auth is only configurable in the [Enterprise version](enterprise.md) of BuildBuddy.
 
 ## Section
 
-```auth:``` The Auth section enables BuildBuddy authentication using an OpenID Connect provider that you specify. **Optional**
-
+`auth:` The Auth section enables BuildBuddy authentication using an OpenID Connect provider that you specify. **Optional**
 
 ## Options
-* ```oauth_providers:``` A list of configured OAuth Providers.
-  * ```issuer_url: ``` The issuer URL of this OIDC Provider.
-  * ```client_id: ``` The oauth client ID.
-  * ```client_secret: ``` The oauth client secret.
-* ```enable_anonymous_usage:``` If true, unauthenticated build uploads will still be allowed but won't be associated with your organization.
+
+- `oauth_providers:` A list of configured OAuth Providers.
+  - `issuer_url: ` The issuer URL of this OIDC Provider.
+  - `client_id: ` The oauth client ID.
+  - `client_secret: ` The oauth client secret.
+- `enable_anonymous_usage:` If true, unauthenticated build uploads will still be allowed but won't be associated with your organization.
+
 ## Google auth provider
 
 If you'd like to use Google as an auth provider, you can easily obtain your client id and client secret [here](https://console.developers.google.com/apis/credentials).
@@ -32,4 +34,4 @@ auth:
     - issuer_url: "https://accounts.google.com"
       client_id: "12345678911-f1r0phjnhbabcdefm32etnia21keeg31.apps.googleusercontent.com"
       client_secret: "sEcRetKeYgOeShErE"
-```
+```

docs/config-cache.md

@@ -5,28 +5,32 @@
   "priority": 500
 }
 -->
+
 # Cache Configuration
 
 ## Section
 
-```cache:``` The cache section enables the BuildBuddy cache and configures how and where it will store data. **Optional**
+`cache:` The cache section enables the BuildBuddy cache and configures how and where it will store data. **Optional**
 
 ## Options
 
 **Optional**
 
-* ```max_size_bytes:``` How big to allow the cache to be (in bytes).
+- `max_size_bytes:` How big to allow the cache to be (in bytes).
+
+- `in_memory:` Whether or not to use the in_memory cache.
 
-* ```in_memory:``` Whether or not to use the in_memory cache.
+- `disk:` The Disk section configures a disk-based cache.
 
-* ```disk:``` The Disk section configures a disk-based cache.
+  - `root_directory` The root directory to store cache data in, if using the disk cache. This directory must be readable and writable by the BuildBuddy process. The directory will be created if it does not exist.
 
-  - ```root_directory``` The root directory to store cache data in, if using the disk cache. This directory must be readable and writable by the BuildBuddy process. The directory will be created if it does not exist.
+- `redis_target`: A redis target for improved RBE performance. ** Enterprise only **
 
 ## Example section
+
 ```
 cache:
   max_size_bytes: 10000000000  # 10 GB
   disk:
     root_directory: /tmp/buildbuddy-cache
-```
+```

docs/config-database.md

@@ -5,17 +5,18 @@
   "priority": 700
 }
 -->
+
 # Database Configuration
 
 ## Section
 
-```database:``` The database section configures the database that BuildBuddy stores metadata in. **Required**
+`database:` The database section configures the database that BuildBuddy stores metadata in. **Required**
 
 ## Options
 
 **Required**
 
-* ```data_source```  This is a connection string used by the database driver to connect to the database. MySQL and SQLite databases are supported.
+- `data_source` This is a connection string used by the database driver to connect to the database. MySQL and SQLite databases are supported.
 
 ## Example sections
 
@@ -31,4 +32,4 @@ database:
 ```
 database:
   data_source: "mysql://buildbuddy_user:pAsSwOrD@tcp(12.34.56.78)/buildbuddy_db"
-```
+```

docs/config-flags.md

@@ -5,10 +5,11 @@
   "priority": 100
 }
 -->
+
 # BuildBuddy Flags
 
 There are several configuration options that are not in the BuildBuddy configuration file. These are:
 
-* ```--listen``` The interface that BuildBuddy will listen on. Defaults to 0.0.0.0 (all interfaces)
-* ```--port``` The port to listen for HTTP traffic on. Defaults to 8080.
-* ```--grpc_port``` The port to listen for gRPC traffic on. Defaults to 1985.
+- `--listen` The interface that BuildBuddy will listen on. Defaults to 0.0.0.0 (all interfaces)
+- `--port` The port to listen for HTTP traffic on. Defaults to 8080.
+- `--grpc_port` The port to listen for gRPC traffic on. Defaults to 1985.

docs/config-github.md

@@ -7,35 +7,39 @@
 -->
 
 # Github Configuration
+
 In order to configure BuildBuddy's GitHub integration, you'll either need to:
+
 - [create an access token](https://docs.github.com/en/github/authenticating-to-github/creating-a-personal-access-token) with the `repo:status` scope. This is the supported method for BuildBuddy open source.
-- or [create a Github Oauth app](https://docs.github.com/en/developers/apps/creating-an-oauth-app). In the `Authorization callback URL` field - you'll need to enter your BuildBuddy application url, followed by the path `/auth/`. For example: `https://https://app.buildbuddy.io/auth/`. This is the recommended method for BuildBuddy Enterprise. 
+- or [create a Github Oauth app](https://docs.github.com/en/developers/apps/creating-an-oauth-app). In the `Authorization callback URL` field - you'll need to enter your BuildBuddy application url, followed by the path `/auth/`. For example: `https://https://app.buildbuddy.io/auth/`. This is the recommended method for BuildBuddy Enterprise.
 
 ## Section
 
-```github:``` The Github section enables the posting of BuildBuddy Github commit statuses for CI runs. **Optional**
+`github:` The Github section enables the posting of BuildBuddy Github commit statuses for CI runs. **Optional**
 
 ## Options
 
 **Optional**
 
-* ```access_token:``` The GitHub access token used to post GitHub commit statuses.
+- `access_token:` The GitHub access token used to post GitHub commit statuses.
 
-* ```client_id:``` The client ID of your Github Oauth App. [ENTERPRISE ONLY]
+- `client_id:` The client ID of your Github Oauth App. [ENTERPRISE ONLY]
 
-* ```client_secret:``` The client secret of your Github Oauth App. [ENTERPRISE ONLY]
+- `client_secret:` The client secret of your Github Oauth App. [ENTERPRISE ONLY]
 
 ## Example section
 
 Open source with access token:
+
 ```
 github:
   access_token: abc123
 ```
 
 Enterprise with Oauth app:
+
 ```
 github:
   client_id: abc123
   client_secret: def456
-```
+```

docs/config-integrations.md

@@ -5,19 +5,20 @@
   "priority": 300
 }
 -->
+
 # Integration Configuration
 
 ## Section
 
-```integrations:``` A section configuring optional external services BuildBuddy can integrate with, like Slack. **Optional**
+`integrations:` A section configuring optional external services BuildBuddy can integrate with, like Slack. **Optional**
 
 ## Options
 
 **Optional**
 
-* ```slack:```  A section configuring Slack integration.
+- `slack:` A section configuring Slack integration.
 
-  * ```webhook_url``` A webhook url to post build update messages to.
+  - `webhook_url` A webhook url to post build update messages to.
 
 ## Getting a webhook url
 
@@ -29,4 +30,4 @@ For more instructions on how to get a Slack webhook url, see the [Slack webhooks
 integrations:
   slack:
     webhook_url: "https://hooks.slack.com/services/AAAAAAAAA/BBBBBBBBB/1D36mNyB5nJFCBiFlIOUsKzkW"
-```
+```

docs/config-misc.md

@@ -5,23 +5,24 @@
   "priority": 200
 }
 -->
+
 # Miscellaneous Configuration
 
 ## BuildEventProxy Section
-```build_event_proxy:```  The BuildEventProxy section configures proxy behavior, allowing BuildBuddy to forward build events to other build-event-protocol compatible servers. **Optional**
+
+`build_event_proxy:` The BuildEventProxy section configures proxy behavior, allowing BuildBuddy to forward build events to other build-event-protocol compatible servers. **Optional**
 
 ## Options
 
 **Optional**
 
-* ```hosts```  A list of host strings that BuildBudy should connect and forward events to.
+- `hosts` A list of host strings that BuildBudy should connect and forward events to.
 
 ## Example section
+
 ```
 build_event_proxy:
   hosts:
     - "grpc://localhost:1985"
     - "grpc://events.buildbuddy.io:1985"
 ```
-
-