build warning fixes

connectors/v/latest/amqp-documentation.adoc

@@ -1,12 +1,3 @@
-:toc:               left
-:toc-title:         AMQP Connector
-:toclevels:         2
-:last-update-label!:
-:docinfo:
-:source-highlighter: coderay
-:icons: font
-
-
 = AMQP Connector Documentation Reference
 
 +++
@@ -372,7 +363,7 @@ AMQP Listener for Queues, allows to listen for incoming messages.
 ** EXPLICIT
 ** SHUTDOWN
 ** UNUSED
- | Defines when the declared queue must be removed from the broker. | EXPLICIT | {nbsp}
+| Defines when the declared queue must be removed from the broker. | EXPLICIT | {nbsp}
 | Exchange to Bind | String | Defines the exchange to bind the queue to. | {nbsp} | {nbsp}
 |======================
 
@@ -388,14 +379,14 @@ AMQP Listener for Queues, allows to listen for incoming messages.
 ** EXPLICIT
 ** SHUTDOWN
 ** UNUSED
- | Defines when the declared exchange must be removed from the broker.| EXPLICIT | {nbsp}
+| Defines when the declared exchange must be removed from the broker.| EXPLICIT | {nbsp}
 | Exchange Type a| Enumeration, one of:
 
 ** DIRECT
 ** TOPIC
 ** FANOUT
 ** HEADERS
- |The type of the exchange to be declared| FANOUT | {nbsp}
+|The type of the exchange to be declared| FANOUT | {nbsp}
 |======================
 
 [[AmqpAttributes]]

connectors/v/latest/common-dynamic-connections.adoc

@@ -9,8 +9,8 @@ To accommodate these use cases, the `config` element supports expressions, which
 
 The next examples shows a dynamic multicast app that:
 
-<1> Defines a `config` for the connector in which the `host`, `username`, and `password` are expressions.
-<2> Describes a flow in which content is posted through HTTP.
-<3> Uses the File connector to read a CSV file that contains a random set of SFTP destinations with columns such as host, user, and port.
-<4> Uses a `<foreach>` component to iterate over each of the lines in the CSV file.
-<5> On each `<foreach>` iteration, resolves each expression in the connector `config` to a different value, establishing different connections to each of the servers.
+. Defines a `config` for the connector in which the `host`, `username`, and `password` are expressions.
+. Describes a flow in which content is posted through HTTP.
+. Uses the File connector to read a CSV file that contains a random set of SFTP destinations with columns such as host, user, and port.
+. Uses a `<foreach>` component to iterate over each of the lines in the CSV file.
+. On each `<foreach>` iteration, resolves each expression in the connector `config` to a different value, establishing different connections to each of the servers.

connectors/v/latest/db-connector-query.adoc

@@ -97,7 +97,7 @@ The fetchSize is a hint to the JDBC driver and need not always be enforced. The
 
 == Setting a query timeout
 
-= Query Timeout Reference
+== Query Timeout Reference
 
 Sometimes database queries take a long time to execute. The following factors often cause delays in query execution:
 

connectors/v/latest/xml-xslt.adoc

@@ -120,17 +120,17 @@ In a more complex use case, the script you use might depend on some external con
 [source, xml, linenums]
 ----
 <flow name="multitenantExample">
-    <http:listener path="transform" allowedMethods="POST" config-ref="httpListener" /> // <1>
+    <http:listener path="transform" allowedMethods="POST" config-ref="httpListener" /> // 1
     <file:read path="#['xslt/$(attributes.queryParam.userId).xslt']" target="xslt" />
     <xml-module:xslt-transform>
         <xml-module:xslt>#[vars.xslt]</xml-module:xslt>
     </xml-module:xslt-transform>
 </flow>
 ----
 
-<1> This flow is triggered through an HTTP request.
-<2> Assuming that the `userId` is provided as a query parameter, the example uses the File connector to read the file that contains the correct XSL and store it in a variable.
-<3> The example executes a transformation using an expression to point to the XSL sheet obtained through the Read operation.
+. This flow is triggered through an HTTP request.
+. Assuming that the `userId` is provided as a query parameter, the example uses the File connector to read the file that contains the correct XSL and store it in a variable.
+. The example executes a transformation using an expression to point to the XSL sheet obtained through the Read operation.
 
 Note that the HTTP and File connectors are simply used as examples. They are not required to perform similar use cases.
 
@@ -154,13 +154,12 @@ The XML module, like the XSL language, provides context properties that can pass
     <xml-module:context-properties>#[{'vtn' : 'some value'}] // <3> </xml-module:context-properties>
 </xml-module:xslt-transform>
 ----
-
 <1> The XSL style sheet declares a `param` called `vtn`.
 <2> The style sheet references the assigned value of the `param` using the `$` prefix.
 <3> The example use the `context-properties` parameter to pass the values in.
 
 
-== Output Mime Type
+== Output MIME Type
 
 The most common use case for XSLT is to output a new XML document. However, XSLT can produce documents in other formats, such as JSON, CSV, or simply a text or number value. Because of this, the produced value will not have any specific mime type assigned. It is recommended that you specify one using the `outputMimeType` parameter.
 

healthcare-toolkit/v/2.0/testing-with-hapi-testpanel.adoc

@@ -58,7 +58,7 @@ In the `Send ACK` scope, an link:/healthcare-toolkit/v/2.0/hl7-ack-component-
 
 In the `To XML and file` scope, the first building block, an link:/healthcare-toolkit/v/2.0/hl7-encoding-transformer[HL7 Encoding Transformer] transforms the original HL7 message from ER7 to XML, and a link:/mule-user-guide/v/3.7/file-connector[File Endpoint] writes the output to a file (in this example, `/tmp/hl7-2test`).
 
-==== HAPI TestPanel Configuration
+== HAPI TestPanel Configuration
 
 This section explains how to set up HAPI TestPanel to work with this example.
 

healthcare-toolkit/v/3.0/connector-testpanel.adoc

@@ -60,7 +60,7 @@ image:testpanel-obj-builder.png[testpanel-obj-builder]
 
 In the *Send a HL7 ACK* scope, HL7 MLLP sends the ACK message to the originating application.
 
-====  TestPanel Configuration
+===  TestPanel Configuration
 
 This section explains how to set up TestPanel to work with this example.
 

tcat-server/v/7.1.0/integrating-with-maven.adoc

@@ -82,7 +82,7 @@ For a complete and working example of a Maven POM file that you can download and
 +
 You can edit this XML to configure it to change the behavior, such as building and inserting your own webapp version strings, etc.
 
-= Maven Publishing Plug-in
+== Maven Publishing Plug-in
 
 * <<Adding the Tcat Server Repository to the POM>>
 * <<Configuring the Plug-in>>

tcat-server/v/7.1.0/managing-users-and-groups.adoc

@@ -9,23 +9,23 @@ You manage users and user groups on the Administration tab in Tcat Server. You c
 
 This section describes how to create, edit, and delete a user in Tcat Server.
 
-==== Create a User
+=== Create a User
 
 . On the Administration tab, click *Users*, and click *New*.
 . Enter the user name that the user enters when they log in to Tcat Server, as well as the user's full name, email address, and password (at least five characters).
 . Select at least one user group that you want this user to have.
 The default user groups are Administrator and User. If you need to create more user groups, see Managing User Groups below.
 . Click *Save*.
 
-==== Edit a User
+=== Edit a User
 
 . On the Administration tab, click *Users*, and  click the user name of the user you want to edit.
 . Edit the user's name or email address if needed.
 . If you need to reset the user's password, click *Reset Password*, enter the new password twice, and then click *OK*.
 . To assign a user group to the user, select it in the Available User Groups list and click *>*. To remove that user group from the user, select it in the Joined User Groups list and click *<*.
 . When you have finished editing this user, click *Save*.
 
-==== Delete a User
+=== Delete a User
 
 . On the Administration tab, click *Users*, and  click the user name of the user you want to delete.
 . Click *Delete*.
@@ -52,7 +52,7 @@ There are two categories of permissions in Tcat - those which are global (displa
 
 Let's say you want to give a user the ability to only view servers in the all server groups. To do this, select the group All from the drop down box and select the "Server - View" permission. If you wanted this user to only have the ability to view servers for the Production group, then you would uncheck the permission for the All group, select Production from the server group drop down box, and then select the "Server - View" permission.
 
-==== Create a User Group
+=== Create a User Group
 
 . On the Administration tab, click *User Groups* in the left pane, and then click *New*.
 . Enter a name for this user group and click *Save*.
@@ -61,7 +61,7 @@ The new user group appears in the user group list.
 . When you finish creating the user groups you want, click *Save*.
 . To assign this user group to a user, edit the user as described above.
 
-==== Edit a User Group
+=== Edit a User Group
 
 . On the Administration tab, click *User Groups*.
 . Edit the assigned permissions as needed.
@@ -71,7 +71,7 @@ The new user group appears in the user group list.
 +
 . When you finish editing user groups, click *Save*.
 
-==== Delete a User Group
+=== Delete a User Group
 
 . On the Administration tab, click *User Groups*, and  click the name of the user group you want to delete.
 Note: You cannot delete the Administrator user group.