Resolving build warnings

Author: tylerkelly13

modules/ROOT/nav.adoc

@@ -6,6 +6,8 @@ This is a nav file. the following info is for reference only at this time.
 :type: index
 ////
 
+* link:{product_homepage}/get-tiny/[+++<svg xmlns="http://www.w3.org/2000/svg" width="16" height="16" viewBox="0 0 16 16"> <path fill="#3F3F3F" fill-rule="evenodd" d="M8 12c-.3 0-.5-.1-.7-.3L1.6 6 3 4.6l4 4V0h2v8.6l4-4L14.4 6l-5.7 5.7c-.2.2-.4.3-.7.3zm-7 2h14v2H1v-2z"></path> </svg>+++ Get TinyMCE] Get TinyMCE]
+
 * xref:quick-start.adoc[]
 
 * General configuration guide

modules/ROOT/pages/advanced/annotations.adoc

@@ -17,7 +17,7 @@ anchor:usingtheannotatorplugin[historical anchor]
 
 To set up the TinyMCE Annotation plugin, perform the following procedure:
 
-[[1-configure-the-annotate-button]]
+[[configure-the-annotate-button]]
 === 1. Configure the Annotate Button
 anchor:1configuretheannotatebutton[historical anchor]
 
@@ -41,7 +41,7 @@ setup: function(ed) {
 
 See link:{rootDir}configure/index.html[Configure TinyMCE] for more information on how to configure TinyMCE core.
 
-[[2-registering-the-annotator-plugin]]
+[[registering-the-annotator-plugin]]
 === 2. Registering the Annotator Plugin
 anchor:2registeringtheannotatorplugin[historical anchor]
 
@@ -68,7 +68,7 @@ This will register an annotation with the name `alpha`. In our example, when an
 NOTE: The data passed through here is the same as the data specified when calling the annotate API. `decorate` is used to turn the annotation data into a document object model (DOM) representation.
 The uid passed through to `decorate` is either the uid field in the data object (if it exists), or a randomly generated uid if it doesn't. Annotator will be responsible for putting the uid on the span. The user does not need to do that part.
 
-[[3-making-the-plugin-available]]
+[[making-the-plugin-available]]
 === 3. Making the Plugin Available
 anchor:3makingthepluginavailable[historical anchor]
 
@@ -79,7 +79,7 @@ For adding the annotate tool to the toolbar that is registered with `alpha` set
   toolbar: "annotate-alpha"
 ----
 
-[[4-applying-annotations]]
+[[applying-annotations]]
 === 4. Applying Annotations
 anchor:4applyingannotations[historical anchor]
 
@@ -107,7 +107,7 @@ Example of specifying your own `uid`:
   });
 ----
 
-[[5-listening-to-selection-events]]
+[[listening-to-selection-events]]
 === 5. Listening to Selection Events
 anchor:5listeningtoselectionevents[historical anchor]
 

modules/ROOT/pages/advanced/handle-async-image-uploads.adoc

@@ -19,7 +19,7 @@ To avoid this situation, it is recommended that the `editor.uploadImages()` func
 Examples of this function are below:
 
 [[using-uploadimages-with-jquery]]
-==== Using uploadImages with jQuery
+== Using uploadImages with jQuery
 anchor:usinguploadimageswithjquery[historical anchor]
 
 [source,js]
@@ -32,7 +32,7 @@ tinymce.activeEditor.uploadImages(function(success) {
 ----
 
 [[using-uploadimages-and-then-posting-a-form]]
-==== Using uploadImages and then posting a form
+== Using uploadImages and then posting a form
 anchor:usinguploadimagesandthenpostingaform[historical anchor]
 
 [source,js]
@@ -43,7 +43,7 @@ tinymce.activeEditor.uploadImages(function(success) {
 ----
 
 [[image-uploader-requirements]]
-==== Image Uploader requirements
+== Image Uploader requirements
 anchor:imageuploaderrequirements[historical anchor]
 
 To upload local images to the remote server, you will need a server-side upload handler script that accepts the images on the server, stores them appropriately, and returns a JSON object containing the location that they were uploaded to.
@@ -70,7 +70,7 @@ This server-side upload handler must return a JSON object that contains a "locat
 ----
 
 [[image-uploader-options]]
-==== Image Uploader options
+=== Image Uploader options
 anchor:imageuploaderoptions[historical anchor]
 
 Multiple configuration options will affect the operation of this feature.  These options are listed below.
@@ -106,7 +106,7 @@ tinymce.init({
 ----
 
 [[rolling-your-image-handler]]
-==== Rolling your image handler
+=== Rolling your image handler
 anchor:rollingyourimagehandler[historical anchor]
 
 If the default behavior of TinyMCE's image upload logic is not right for you, you may set your behavior by using the images_upload_handler configuration property.
@@ -152,7 +152,7 @@ xhr.send(formData);   } });
 ----
 
 [[cors-considerations]]
-==== CORS considerations
+=== CORS considerations
 anchor:corsconsiderations[historical anchor]
 
 You may choose for your web application to upload image data to a separate domain. If so, you will need to configure http://en.wikipedia.org/wiki/Cross-origin_resource_sharing[Cross-origin resource sharing (CORS)] for your application to comply with JavaScript "same origin" restrictions.

modules/ROOT/pages/advanced/php-upload-handler.adoc

@@ -11,7 +11,7 @@ The following script creates a server-side upload handler in PHP suitable for us
 Please note that this script is provided for your reference - you'll need to update this as necessary for your application.
 
 [[example-postacceptorphp]]
-===== Example postAcceptor.php
+== Example postAcceptor.php
 anchor:examplepostacceptorphp[historical anchor]
 
 [source,php]

modules/ROOT/pages/advanced/usage-with-module-loaders.adoc

@@ -11,7 +11,7 @@ TinyMCE can easily be installed with `npm` and used with module loaders such as
 The first thing you have to decide is how to load your modules.
 
 [[es2015-modules]]
-=== ES2015 modules
+== ES2015 modules
 anchor:es2015modules[historical anchor]
 
 If you are using ES2015 modules, a simple example could look something like this.
@@ -36,7 +36,7 @@ tinymce.init({
 ----
 
 [[commonjs-modules]]
-=== CommonJS modules
+== CommonJS modules
 anchor:commonjsmodules[historical anchor]
 
 If you are using CommonJS modules, the example looks pretty much the same, only using the different `require` function to import the dependencies.

modules/ROOT/pages/api/tinymce.dom/tinymce.dom.domquery.adoc

@@ -413,7 +413,7 @@ grep(array:Array, callback:function):Array
 
 Filters out items from the input array by calling the specified function for each item. If the function returns false the item will be excluded if it returns true it will be included.
 
-[[examples]]
+[[examples-grep]]
 ==== Examples
 
 [source,js]

modules/ROOT/pages/api/tinymce.dom/tinymce.dom.domutils.adoc

@@ -138,7 +138,7 @@ add(parentElm:String, name:String, attrs:Object, html:String, create:Boolean):El
 
 Adds the specified element to another element or elements.
 
-[[examples]]
+[[examples-add]]
 ==== Examples
 
 [source,js]

modules/ROOT/pages/api/tinymce.dom/tinymce.dom.selection.adoc

@@ -83,7 +83,7 @@ getBookmark(type:Number, normalized:Boolean):Object
 
 Returns a bookmark location for the current selection. This bookmark object can then be used to restore the selection after some content modification to the document.
 
-[[examples]]
+[[examples-getbookmark]]
 ==== Examples
 
 [source,js]

modules/ROOT/pages/api/tinymce.html/tinymce.html.domparser.adoc

@@ -34,7 +34,7 @@ addAttributeFilter(callback:function)
 
 Adds a attribute filter function to the parser, the parser will collect nodes that has the specified attributes and then execute the callback once it has finished parsing the document.
 
-[[examples]]
+[[examples-addattributefilter]]
 ==== Examples
 
 [source,js]

modules/ROOT/pages/api/tinymce.html/tinymce.html.node.adoc

@@ -67,7 +67,7 @@ append(node:tinymce.html.Node):tinymce.html.Node
 
 Appends a new node as a child of the current node.
 
-[[examples]]
+[[examples-append]]
 ==== Examples
 
 [source,js]