Make it clear that this is just a snippet

Author: michaelklishin

docs/feature-flags/index.md

@@ -278,10 +278,12 @@ There are two ways to do this:
  2. Using the `forced_feature_flags_on_init` setting in [`advanced.config`](./configure):
 
     ```erlang
+    %% ...
     {rabbit, [
       %% this is just an example, in practice this list will be much longer
       {forced_feature_flags_on_init, [quorum_queue, implicit_default_bindings]}
-    ]}
+    ]},
+    %% ...
     ```
 
 The environment variable has precedence over the configuration parameter.

versioned_docs/version-3.13/feature-flags/index.md

@@ -289,10 +289,12 @@ There are two ways to do this:
  2. Using the `forced_feature_flags_on_init` setting in [`advanced.config`](./configure):
 
     ```erlang
+    %% ...
     {rabbit, [
       %% this is just an example, in practice this list will be much longer
       {forced_feature_flags_on_init, [quorum_queue, implicit_default_bindings]}
-    ]}
+    ]},
+    %% ...
     ```
 
 The environment variable has precedence over the configuration parameter.

versioned_docs/version-4.0/feature-flags/index.md

@@ -278,10 +278,12 @@ There are two ways to do this:
  2. Using the `forced_feature_flags_on_init` setting in [`advanced.config`](./configure):
 
     ```erlang
+    %% ...
     {rabbit, [
       %% this is just an example, in practice this list will be much longer
       {forced_feature_flags_on_init, [quorum_queue, implicit_default_bindings]}
-    ]}
+    ]},
+    %% ...
     ```
 
 The environment variable has precedence over the configuration parameter.