Fixing codeblocks and notes?

Author: tylerkelly13

CONTRIBUTING.adoc

@@ -40,40 +40,40 @@ Include any key values pairs and method options that are required to enable a us
 
 For example, this is good:
 
-`
+----
 tinymce.init({
   selector: 'textarea',  // change this value according to your HTML
   plugins: 'codesample',
   toolbar: 'codesample'
 });
-`
+----
 
 This is not:
 
-`+
+----
 tinymce.init({
   ...
   plugins: 'codesample',
   toolbar: 'codesample'
   ...
 });
-+`
+----
 
 === URLs and links
 
 Resources to be linked take the form of placing the linked text between brackets and the URL between parenthesis. Linking an external resource looks like this:
 
-`+
+----
 hello, [text to link](http://www.example.com) to the URL example.com.
-+`
+----
 
 === Codepens
 
 Codepens can be added to content using the "codepen.html" include, such as:
 
-`
+----
 {% include codepen.html id="basic-example" %}
-`
+----
 
 There are several options for this include file - please see `_includes/codepen.html` for details.
 
@@ -83,7 +83,7 @@ The source for each CodePen is store in the `_includes/codepens/` directory.
 
 Every page should have a meta section starting at line 1 containing information that is both informative and system critical. If you are creating a page or editing one that currently has inadequate meta information, please read the comments next to the default meta fields below.
 
-`
+----
 ---                // Three dashes at the start and end of the meta section, must be included.
 layout: default    // In most cases leave this as 'default'.
 title:             // The nav.yml references this so it must be included and it should be brief.
@@ -92,7 +92,7 @@ description_short: // Short description for the grid layouts.
 description:       // Detailed description at page level for the header section under the title.
 keywords:          // Space-separated list of keywords in the content.
 ---
-`
+----
 
 == Style Guide
 

README.adoc

@@ -33,29 +33,29 @@ The following procedure assists with building (or compiling) the documentation l
 You need the following programs installed on your computer:
 
 * Ruby version 2 or later. To verify the installed version, run:
-`
+----
 ruby --version
-`
+----
 
 . Install git, g{pp}, `make`, and the zlib development files. For example:
  ** On Fedora, run:
 +
-`pass:c[
+----
 sudo dnf install git-all gcc-c++ make zlib-devel
-]`
+----
 
  ** On Ubuntu, Debian or their derivatives, run:
-`
+----
 sudo apt install git gcc cpp make zlib1g-dev
-`
+----
 . Install Ruby Nokogiri: \https://nokogiri.org/
  `
  sudo gem install nokogiri
-`
+----
 . Install Ruby Bundler. Install using:
  `
  sudo gem install bundler
-`
+----
 . (optional) Docker
 
 ===== Windows users
@@ -67,18 +67,18 @@ If you are a Windows user, follow these steps to work on TinyMCE documentation:
 . Run the following command on a command prompt to install Ruby Bundler:
  `
  gem install bundler
-`
+----
 
 ===== Mac OS users
 
 . Ruby version 2 or later is required. Verify the pre-installed version, using:
  `
  ruby --version
-`
+----
 . Install Ruby Bundler, using:
  `
  gem install bundler
-`
+----
 
 ==== First time set up
 
@@ -87,23 +87,23 @@ Once you have installed any missing prerequisites, in a terminal or on a command
 . Clone the git repository:
  `
  git clone [email protected]:tinymce/tinymce-docs.git
-`
+----
 . Change directory into the cloned git repository:
  `
  cd tinymce-docs
-`
+----
 . Run the initialization script to install dependencies and create the required local files in the git repository:
  `
  ./_scripts/init.sh
-`
+----
 
 ==== Run the development version of the documentation
 
 To create a development version of the documentation, run:
 
-`
+----
 ./_scripts/serve.sh
-`
+----
 
 Allow the `serve.sh` script to run in the background while you are working on the TinyMCE documentation.
 
@@ -124,34 +124,34 @@ The TinyMCE API documentation is maintained within the https://github.com/tinymc
 
 To install MoxieDoc, run:
 
-`
+----
 npm install -g git://github.com/tinymce/moxiedoc.git
-`
+----
 
 ===== Run the development version of the documentation for the current TinyMCE version
 
 . Download the TinyMCE version in the `.api-version` file in this project's root directory and extract the API documentation using:
-`
+----
  ./_scripts/api-reference.sh
-`
+----
 . Start the development server using:
-`
+----
  ./_scripts/serve.sh
-`
+----
 
 ===== Run the development version of the documentation for a local TinyMCE repository
 
 . Extract the API documentation from a local copy of the TinyMCE repository using:
-`
+----
  ./_scripts/api-reference-local.sh <path/to/the/tinymce/repo>
-`
+----
 . Start the development server using:
-`
+----
  ./_scripts/serve.sh
-`
+----
 . To include updates made to the TinyMCE API documentation in the TinyMCE repository, run the `api-reference-local` script:
-`
+----
  ./_scripts/api-reference-local.sh <path/to/the/tinymce/repo>
-`
+----
 
 NOTE: The development server does not need to be stopped prior to running the `api-reference-local` script.

_includes/configuration/allow-conditional-comments.adoc

@@ -10,9 +10,10 @@ This option allows you to specify whether the editor should parse and keep condi
 
 ===== Example
 
-`js
+[source,js]
+----
 tinymce.init({
   selector: 'textarea',  // change this value according to your HTML
   allow_conditional_comments: true
 });
-`
+----

_includes/configuration/allow-html-in-named-anchor.adoc

@@ -10,9 +10,10 @@ This option allows you to specify whether the editor should parse and keep `html
 
 ===== Example
 
-`js
+[source,js]
+----
 tinymce.init({
   selector: 'textarea',  // change this value according to your HTML
   allow_html_in_named_anchor: true
 });
-`
+----

_includes/configuration/allow-script-urls.adoc

@@ -10,9 +10,10 @@ Enabling this option will allow `javascript: urls` in links and images. This is
 
 ===== Example
 
-`js
+[source,js]
+----
 tinymce.init({
   selector: 'textarea',  // change this value according to your HTML
   allow_script_urls: true
 });
-`
+----

_includes/configuration/allow-unsafe-link-target.adoc

@@ -10,9 +10,10 @@ By default all links with a `target` of __blank_ will get a `rel` attribute of `
 
 ===== Example
 
-`js
+[source,js]
+----
 tinymce.init({
   selector: 'textarea',
   allow_unsafe_link_target: true
 });
-`
+----

_includes/configuration/anchor-bottom.adoc

@@ -8,18 +8,20 @@ Lets you specify a custom name for the bottom anchor in the url type ahead drop
 
 ===== Example of custom value
 
-`js
+[source,js]
+----
 tinymce.init({
   selector: 'textarea',
   anchor_bottom: '#mybottom'
 });
-`
+----
 
 ===== Example of disabling
 
-`js
+[source,js]
+----
 tinymce.init({
   selector: 'textarea',
   anchor_bottom: false
 });
-`
+----

_includes/configuration/anchor-top.adoc

@@ -8,18 +8,20 @@ Lets you specify a custom name for the top anchor in the url type ahead drop dow
 
 ===== Example of custom value
 
-`js
+[source,js]
+----
 tinymce.init({
   selector: 'textarea',
   anchor_top: '#mytop'
 });
-`
+----
 
 ===== Example of disabling
 
-`js
+[source,js]
+----
 tinymce.init({
   selector: 'textarea',
   anchor_top: false
 });
-`
+----

_includes/configuration/auto-focus.adoc

@@ -6,9 +6,10 @@ Automatically set the focus to an editor instance. The value of this option shou
 
 ===== Example
 
-`js
+[source,js]
+----
 tinymce.init({
   selector: 'textarea',  // change this value according to your HTML
   auto_focus: 'element1'
 });
-`
+----

_includes/configuration/automatic-uploads.adoc

@@ -12,10 +12,11 @@ WARNING: Note that, this option will do nothing if `images_upload_url` is not sp
 
 ===== Example
 
-`js
+[source,js]
+----
 tinymce.init({
   selector: 'textarea',  // change this value according to your HTML
   images_upload_url: 'postAcceptor.php',
   automatic_uploads: false
 });
-`
+----