DEV: fix toc issue on several pages (#525)

* DEV: fix toc issue on several pages

* Update content/develop/connect/cli.md

Co-authored-by: andy-stark-redis <164213578+andy-stark-redis@users.noreply.github.com>

---------

Co-authored-by: andy-stark-redis <164213578+andy-stark-redis@users.noreply.github.com>

Author: dwdougherty

content/develop/connect/cli.md

@@ -144,7 +144,7 @@ If the target server requires authentication using a client side certificate,
 you can specify a certificate and a corresponding private key using `--cert` and
 `--key`.
 
-## Getting input from other programs
+## Get input from other programs
 
 There are two ways you can use `redis-cli` in order to receive input from other
 commands via the standard input. One is to use the target payload as the last argument
@@ -235,7 +235,7 @@ A CSV (Comma Separated Values) output feature exists within `redis-cli` to expor
 
 Note that the `--csv` flag will only work on a single command, not the entirety of a DB as an export.
 
-## Running Lua scripts
+## Run Lua scripts
 
 The `redis-cli` has extensive support for using the debugging facility
 of Lua scripting, available with Redis 3.2 onwards. For this feature, refer to the [Redis Lua debugger documentation]({{< relref "/develop/interact/programmability/lua-debugging" >}}).
@@ -261,8 +261,7 @@ So `location:hastings:temp` will populate the [`KEYS`]({{< relref "/commands/key
 The `--eval` option is useful when writing simple scripts. For more
 complex work, the Lua debugger is recommended. It is possible to mix the two approaches, since the debugger can also execute scripts from an external file.
 
-Interactive mode
-===
+## Interactive mode
 
 We have explored how to use the Redis CLI as a command line program.
 This is useful for scripts and certain types of testing, however most
@@ -293,7 +292,7 @@ The prompt updates as the connected server changes or when operating on a databa
     127.0.0.1:6379> DBSIZE
     (integer) 503
 
-## Handling connections and reconnections
+### Handle connections and reconnections
 
 Using the `CONNECT` command in interactive mode makes it possible to connect
 to a different instance, by specifying the *hostname* and *port* we want
@@ -346,7 +345,7 @@ testing, but this limitation should be known.
 
 Use the `-t <timeout>` option to specify server timeout in seconds.
 
-## Editing, history, completion and hints
+### Editing, history, completion and hints
 
 Because `redis-cli` uses the
 [linenoise line editing library](http://github.com/antirez/linenoise), it
@@ -372,7 +371,7 @@ syntax hints. Like command history, this behavior can be turned on and off via t
 
 Reverse history searches, such as `CTRL-R` in terminals, is supported.
 
-## Preferences
+### Preferences
 
 There are two ways to customize `redis-cli` behavior. The file `.redisclirc`
 in the home directory is loaded by the CLI on startup. You can override the
@@ -387,7 +386,7 @@ can be set, either by typing the command in the CLI or adding it to the
 * `:set hints` - enables syntax hints
 * `:set nohints` - disables syntax hints
 
-## Running the same command N times
+### Run the same command N times
 
 It is possible to run the same command multiple times in interactive mode by prefixing the command
 name by a number:
@@ -399,7 +398,7 @@ name by a number:
     (integer) 4
     (integer) 5
 
-## Showing help about Redis commands
+### Show online help for Redis commands
 
 `redis-cli` provides online help for most Redis [commands]({{< relref "/commands" >}}), using the `HELP` command. The command can be used
 in two forms:
@@ -433,12 +432,11 @@ For example in order to show help for the [`PFADD`]({{< relref "/commands/pfadd"
 
 Note that `HELP` supports TAB completion as well.
 
-## Clearing the terminal screen
+### Clear the terminal screen
 
 Using the `CLEAR` command in interactive mode clears the terminal's screen.
 
-Special modes of operation
-===
+## Special modes of operation
 
 So far we saw two main modes of `redis-cli`.
 
@@ -460,7 +458,7 @@ are explained in the next sections:
 * Simulating [LRU]({{< relref "/develop/reference/eviction" >}}) workloads for showing stats about keys hits.
 * A client for the Lua debugger.
 
-## Continuous stats mode
+### Continuous stats mode
 
 Continuous stats mode is probably one of the lesser known yet very useful features of `redis-cli` to monitor Redis instances in real time. To enable this mode, the `--stat` option is used.
 The output is very clear about the behavior of the CLI in this mode:
@@ -547,7 +545,7 @@ The `--memkeys` option now works on cluster replicas.
 
 You can use the `--keystats` and `--keystats-samples` options to combine `--memkeys` and `--bigkeys` with additional distribution data.
 
-## Getting a list of keys
+## Get a list of keys
 
 It is also possible to scan the key space, again in a way that does not
 block the Redis server (which does happen when you use a command
@@ -624,7 +622,7 @@ When another client publishes some message in some channel, such as with the com
 This is very useful for debugging Pub/Sub issues.
 To exit the Pub/Sub mode just process `CTRL-C`.
 
-## Monitoring commands executed in Redis
+## Monitor commands executed in Redis
 
 Similarly to the Pub/Sub mode, the monitoring mode is entered automatically
 once you use the [`MONITOR`]({{< relref "/commands/monitor" >}}) command. All commands received by the active Redis instance will be printed to the standard output:
@@ -637,7 +635,7 @@ once you use the [`MONITOR`]({{< relref "/commands/monitor" >}}) command. All co
 Note that it is possible to pipe the output, so you can monitor
 for specific patterns using tools such as `grep`.
 
-## Monitoring the latency of Redis instances
+## Monitor the latency of Redis instances
 
 Redis is often used in contexts where latency is very critical. Latency
 involves multiple moving parts within the application, from the client library
@@ -765,7 +763,7 @@ If you think some of the commands are not replicated correctly in your replicas
 this is a good way to check what's happening, and also useful information
 in order to improve the bug report.
 
-## Performing an LRU simulation
+## Perform an LRU simulation
 
 Redis is often used as a cache with [LRU eviction]({{< relref "/develop/reference/eviction" >}}).
 Depending on the number of keys and the amount of memory allocated for the

content/develop/reference/modules/modules-native-types.md

@@ -9,9 +9,7 @@ categories:
 - oss
 - kubernetes
 - clients
-description: 'How to use native types in a Redis module
-
-  '
+description: How to use native types in a Redis module
 linkTitle: Native types API
 title: Modules API for native types
 weight: 1
@@ -34,8 +32,7 @@ the API exported by the Redis modules system in order to create new data
 structures and handle the serialization in RDB files, the rewriting process
 in AOF, the type reporting via the [`TYPE`]({{< relref "/commands/type" >}}) command, and so forth.
 
-Overview of native types
----
+## Overview of native types
 
 A module exporting a native type is composed of the following main parts:
 
@@ -51,8 +48,7 @@ is available inside the Redis distribution in the `/modules/hellotype.c` file.
 The reader is encouraged to read the documentation by looking at this example
 implementation to see how things are applied in the practice.
 
-Registering a new data type
-===
+## Register a new data type
 
 In order to register a new native type into the Redis core, the module needs
 to declare a global variable that will hold a reference to the data type.
@@ -134,11 +130,7 @@ registration function: `rdb_load`, `rdb_save`, `aof_rewrite`, `digest` and
 * `mem_usage` is called when the [`MEMORY`]({{< relref "/commands/memory" >}}) command asks for the total memory consumed by a specific key, and is used in order to get the amount of bytes used by the module value.
 * `free` is called when a key with the module native type is deleted via [`DEL`]({{< relref "/commands/del" >}}) or in any other mean, in order to let the module reclaim the memory associated with such a value.
 
-Ok, but *why* modules types require a 9 characters name?
----
-
-Oh, I understand you need to understand this, so here is a very specific
-explanation.
+### Why module types require nine character names
 
 When Redis persists to RDB files, modules specific data types require to
 be persisted as well. Now RDB files are sequences of key-value pairs
@@ -186,8 +178,7 @@ we can convert back the 64 bit value into a 9 characters name, and print
 an error to the user that includes the module type name! So that she or he
 immediately realizes what's wrong.
 
-Setting and getting keys
----
+### Set and get keys
 
 After registering our new data type in the `RedisModule_OnLoad()` function,
 we also need to be able to set Redis keys having as value our native type.
@@ -254,8 +245,7 @@ key if there is already one:
     }
     /* Do something with 'data'... */
 
-Free method
----
+### Free method
 
 As already mentioned, when Redis needs to free a key holding a native type
 value, it needs help from the module in order to release the memory. This
@@ -274,8 +264,7 @@ However a more real world one will call some function that performs a more
 complex memory reclaiming, by casting the void pointer to some structure
 and freeing all the resources composing the value.
 
-RDB load and save methods
----
+### RDB load and save methods
 
 The RDB saving and loading callbacks need to create (and load back) a
 representation of the data type on disk. Redis offers a high level API
@@ -352,18 +341,11 @@ Note that while there is no error handling on the API that writes and reads
 from disk, still the load callback can return NULL on errors in case what
 it reads does not look correct. Redis will just panic in that case.
 
-AOF rewriting
----
+### AOF rewriting
 
     void RedisModule_EmitAOF(RedisModuleIO *io, const char *cmdname, const char *fmt, ...);
 
-Handling multiple encodings
----
-
-    WORK IN PROGRESS
-
-Allocating memory
----
+### Allocate memory
 
 Modules data types should try to use `RedisModule_Alloc()` functions family
 in order to allocate, reallocate and release heap memory used to implement the native data structures (see the other Redis Modules documentation for detailed information).

content/develop/reference/sentinel-clients.md

@@ -46,17 +46,15 @@ A Redis client supporting Sentinel can automatically discover the address of a R
 
 This is the procedure a client should follow in order to obtain the master address starting from the list of Sentinels and the service name.
 
-Step 1: connecting to the first Sentinel
----
+### Step 1: connect to the first Sentinel
 
 The client should iterate the list of Sentinel addresses. For every address it should try to connect to the Sentinel, using a short timeout (in the order of a few hundreds of milliseconds). On errors or timeouts the next Sentinel address should be tried.
 
 If all the Sentinel addresses were tried without success, an error should be returned to the client.
 
 The first Sentinel replying to the client request should be put at the start of the list, so that at the next reconnection, we'll try first the Sentinel that was reachable in the previous connection attempt, minimizing latency.
 
-Step 2: ask for master address
----
+### Step 2: ask for the master address
 
 Once a connection with a Sentinel is established, the client should retry to execute the following command on the Sentinel:
 
@@ -71,8 +69,7 @@ The result from this call can be one of the following two replies:
 
 If an ip:port pair is received, this address should be used to connect to the Redis master. Otherwise if a null reply is received, the client should try the next Sentinel in the list.
 
-Step 3: call the ROLE command in the target instance
----
+### Step 3: call the ROLE command in the target instance
 
 Once the client discovered the address of the master instance, it should
 attempt a connection with the master, and call the [`ROLE`]({{< relref "/commands/role" >}}) command in order
@@ -82,8 +79,7 @@ If the [`ROLE`]({{< relref "/commands/role" >}}) commands is not available (it w
 
 If the instance is not a master as expected, the client should wait a short amount of time (a few hundreds of milliseconds) and should try again starting from Step 1.
 
-Handling reconnections
-===
+## Handle reconnections
 
 Once the service name is resolved into the master address and a connection is established with the Redis master instance, every time a reconnection is needed, the client should resolve again the address using Sentinels restarting from Step 1. For instance Sentinel should contacted again the following cases:
 
@@ -92,8 +88,7 @@ Once the service name is resolved into the master address and a connection is es
 
 In the above cases and any other case where the client lost the connection with the Redis server, the client should resolve the master address again.
 
-Sentinel failover disconnection
-===
+## Sentinel failover disconnection
 
 Starting with Redis 2.8.12, when Redis Sentinel changes the configuration of
 an instance, for example promoting a replica to a master, demoting a master to
@@ -107,8 +102,7 @@ If the client will contact a Sentinel with yet not updated information, the veri
 
 Note: it is possible that a stale master returns online at the same time a client contacts a stale Sentinel instance, so the client may connect with a stale master, and yet the ROLE output will match. However when the master is back again Sentinel will try to demote it to replica, triggering a new disconnection. The same reasoning applies to connecting to stale replicas that will get reconfigured to replicate with a different master.
 
-Connecting to replicas
-===
+## Connect to replicas
 
 Sometimes clients are interested to connect to replicas, for example in order to scale read requests. This protocol supports connecting to replicas by modifying step 2 slightly. Instead of calling the following command:
 
@@ -124,21 +118,18 @@ Symmetrically the client should verify with the [`ROLE`]({{< relref "/commands/r
 instance is actually a replica, in order to avoid scaling read queries with
 the master.
 
-Connection pools
-===
+## Connection pools
 
 For clients implementing connection pools, on reconnection of a single connection, the Sentinel should be contacted again, and in case of a master address change all the existing connections should be closed and connected to the new address.
 
-Error reporting
-===
+## Error reporting
 
 The client should correctly return the information to the user in case of errors. Specifically:
 
 * If no Sentinel can be contacted (so that the client was never able to get the reply to `SENTINEL get-master-addr-by-name`), an error that clearly states that Redis Sentinel is unreachable should be returned.
 * If all the Sentinels in the pool replied with a null reply, the user should be informed with an error that Sentinels don't know this master name.
 
-Sentinels list automatic refresh
-===
+## Sentinels list automatic refresh
 
 Optionally once a successful reply to `get-master-addr-by-name` is received, a client may update its internal list of Sentinel nodes following this procedure:
 
@@ -147,8 +138,7 @@ Optionally once a successful reply to `get-master-addr-by-name` is received, a c
 
 It is not needed for a client to be able to make the list persistent updating its own configuration. The ability to upgrade the in-memory representation of the list of Sentinels can be already useful to improve reliability.
 
-Subscribe to Sentinel events to improve responsiveness
-===
+## Subscribe to Sentinel events to improve responsiveness
 
 The [Sentinel documentation]({{< relref "/operate/oss_and_stack/management/sentinel" >}}) shows how clients can connect to
 Sentinel instances using Pub/Sub in order to subscribe to changes in the
@@ -163,7 +153,6 @@ However update messages received via Pub/Sub should not substitute the
 above procedure, since there is no guarantee that a client is able to
 receive all the update messages.
 
-Additional information
-===
+## Additional information
 
 For additional information or to discuss specific aspects of this guidelines, please drop a message to the [Redis Google Group](https://groups.google.com/group/redis-db).