Fix the formatting of the topic.namespace.map documentation

Author: stIncMale

src/main/java/com/mongodb/kafka/connect/source/MongoSourceConfig.java

@@ -219,25 +219,25 @@ public class MongoSourceConfig extends AbstractConfig {
           + " suffixed with the value of `sep` if and only if the value of `coll` is not empty."
           + "\n  - `sep_coll_sep` The value of the `coll` variable"
           + " prefixed and suffixed with the value of `sep` if and only if the value of `coll` is not empty."
-          + "\n To be expanded, a variable must be enclosed between curly brackets '{' and '}', for example '{db}'."
+          + "\n  To be expanded, a variable must be enclosed between curly brackets '{' and '}', for example '{db}'."
           + " The characters '{' and '}' are not allowed to be used in the topic name template for any other purpose."
           + " Note that variable names are case-sensitive."
-          + "\nBe careful when creating a namespace pattern with characters that need escaping according to the JSON syntax."
+          + "\n  Be careful when creating a namespace pattern with characters that need escaping according to the JSON syntax."
           + " For example, if you want to match full stop '.', the regex syntax requires escaping it as '\\.'."
           + " However, reverse solidus '\\' itself must be escaped as '\\\\' according to the JSON syntax."
           + " Consequently, to match '.' you need to write '\\\\.'."
           + "\n- Wildcard. The namespace pattern is asterisk '*' and matches any namespace."
           + " The topic name template is interpreted as the topic name."
-          + "\n The matching order:"
+          + "\nThe matching order:"
           + "\n1. Simple pairs with a collection name in the namespace pattern."
           + "\n2. Simple pairs without a collection name in the namespace pattern."
           + "\n3. Regex pairs in order."
           + "\n4. The wildcard pair."
-          + "\n Matching stops as soon as the first match is found. If no matches are found,"
+          + "\n  Matching stops as soon as the first match is found. If no matches are found,"
           + " the topic name is computed solely based on the namespace. The namespace may either have a collection name, or not:"
-          + "\n- If there is a collection name, then the topic name is computed"
+          + "\n  - If there is a collection name, then the topic name is computed"
           + " by concatenating the database name and the collection name, separated by `topic.separator`."
-          + "\n- If there is no collection name, then the database name is used as the topic name."
+          + "\n  - If there is no collection name, then the database name is used as the topic name."
           + "\nExamples (`topic.separator` is assumed to be '-'):"
           + "\n1. '{\"myDb\": \"topicTwo\", \"myDb.myColl\": \"topicOne\"}'"
           + " The 'myDb.myColl' namespace is mapped to the 'topicOne' topic name."