doc update

Author: Tom Barnes

site/config-overrides.md

@@ -184,8 +184,8 @@ The secret macro `SECRETNAME` field must reference the name of a Kubernetes secr
 * Reference the name of the current bean and each parent bean in any hierarchy you override.
   * Note that the `combine-mode` verbs (`add` and `replace`) should be omitted for beans that are already defined in your original domain home configuration.
   * See [Override template samples](#override-template-samples) for examples.
-* Use situational config `replace` and `add` verbs as follows:
-  * If you are adding a new bean that doesn't already exist in your original domain home configuration, specify `add` on the MBean itself and on each attribute within the bean. 
+* Use situational configuration `replace` and `add` verbs as follows:
+  * If you are adding a new bean that doesn't already exist in your original domain home configuration, then specify `add` on the MBean itself and on each attribute within the bean. 
     * See the `server-debug` stanza in [Override template samples](#override-template-samples) below for an example.
   * If you are adding a new attribute to an existing bean in the domain home configuration, the attribute needs an `add` verb.
     * See the `max-message-size` stanza in [Override template samples](#override-template-samples) below for an example.