Contextual information to precede shared component

Allows for the shared component to accept arbitrary MDX to account for
differences in the nesting of redis configs

Author: bignimbus

docs/shared/redis-tls.mdx

@@ -1,4 +1,6 @@
-For Redis TLS connections, you can set up a client certificate or override the root certificate authority by configuring `tls` in your router's [YAML config file](/graphos/routing/configuration/overview#yaml-config-file). Nest the `tls` configuration under the `redis` section for your feature. For example:
+For Redis TLS connections, you can set up a client certificate or override the root certificate authority by configuring `tls` in your router's [YAML config file](/graphos/routing/configuration/overview#yaml-config-file).
+
+{props.children}
 
 ```yaml
 redis:

docs/source/routing/operations/apq.mdx

@@ -200,7 +200,7 @@ When using the same Redis instance for multiple purposes, the `namespace` option
 
 #### TLS
 
-<RedisTls />
+<RedisTls>Nest the following configuration under `apq.router.cache`:</RedisTls>
 
 #### Required to start
 

docs/source/routing/performance/caching/response-caching/customization.mdx

@@ -256,7 +256,7 @@ or, if configured with multiple URLs:
 
 ### TLS and authentication
 
-<RedisTls />
+<RedisTls>Nest the following configuration under `response_cache.subgraph.all`:</RedisTls>
 
 ### Timeout configuration
 

docs/source/routing/query-planning/caching.mdx

@@ -245,7 +245,7 @@ When using the same Redis instance for multiple purposes, the `namespace` option
 
 #### TLS
 
-<RedisTls />
+<RedisTls>Nest the following configuration under `supergraph.query_planning.cache`:</RedisTls>
 
 #### Required to start
 

docs/source/routing/security/tls.mdx

@@ -130,4 +130,4 @@ tls:
 
 ## Redis TLS configuration
 
-<RedisTls />
+<RedisTls>Nest the `tls` configuration under the `redis` key for your feature—for example, under `apq.router.cache` for APQ caching:</RedisTls>