fixup: no space before and after slash

Signed-off-by: Björn Svensson <[email protected]>

docs/cluster.md

@@ -9,14 +9,14 @@ It is not intended as a complete reference. For that it's always best to refer t
   - [Connecting](#connecting)
   - [Executing commands](#executing-commands)
   - [Executing commands on a specific node](#executing-commands-on-a-specific-node)
-  - [Disconnecting / cleanup](#disconnecting--cleanup)
+  - [Disconnecting/cleanup](#disconnecting-cleanup)
   - [Pipelining](#pipelining)
   - [Events](#events)
 - [Asynchronous API](#asynchronous-api)
   - [Connecting](#connecting-1)
   - [Executing commands](#executing-commands-1)
   - [Executing commands on a specific node](#executing-commands-on-a-specific-node-1)
-  - [Disconnecting / cleanup](#disconnecting--cleanup-1)
+  - [Disconnecting/cleanup](#disconnecting-cleanup-1)
   - [Events](#events-1)
 - [Miscellaneous](#miscellaneous)
   - [Extend the list of supported commands](#extend-the-list-of-supported-commands)
@@ -96,7 +96,7 @@ This function handles `printf`-like arguments similar to `valkeyClusterCommand()
 If the command times out or the connection to the node fails, a slot map update is scheduled to be performed when the next command is sent.
 `valkeyClusterCommandToNode` also performs a slot map update if it has previously been scheduled.
 
-### Disconnecting / cleanup
+### Disconnecting/cleanup
 
 To disconnect and free the context the following function can be used:
 
@@ -267,7 +267,7 @@ status = valkeyClusterAsyncCommandToNode(acc, node, commandCallback, privdata, "
 This functions will only attempt to send the command to a specific node and will not perform redirects or retries, but communication errors will trigger a slot map update just like the commonly used API.
 
 
-### Disconnecting / cleanup
+### Disconnecting/cleanup
 
 Asynchronous cluster connections can be terminated using:
 

docs/standalone.md

@@ -10,7 +10,7 @@ This document describes using `libvalkey` in standalone (non-cluster) mode, incl
   - [Executing commands](#executing-commands)
   - [Using replies](#using-replies)
   - [Reply types](#reply-types)
-  - [Disconnecting / cleanup](#disconnecting--cleanup)
+  - [Disconnecting/cleanup](#disconnecting-cleanup)
   - [Pipelining](#pipelining)
   - [Errors](#errors)
   - [Thread safety](#thread-safety)
@@ -139,7 +139,7 @@ When a `valkeyReply` is returned, you should test the `valkeyReply->type` field
 - `VALKEY_REPLY_ATTR` - An attribute reply. As of yet unused by valkey-server.
 - `VALKEY_REPLY_PUSH` - An out of band push reply. This is also array-like in nature.
 
-### Disconnecting / cleanup
+### Disconnecting/cleanup
 
 When libvalkey returns non-null `valkeyReply` struts you are responsible for freeing them with `freeReplyObject`.  In order to disconnect and free the context simply call `valkeyFree`.