Use HTML inside shortcode blocks

rmccue · rmccue · commit eea2b24a8f33 · 2017-07-18T15:41:51.000+10:00
diff --git a/extending-the-rest-api/routes-and-endpoints.md b/extending-the-rest-api/routes-and-endpoints.md
@@ -20,7 +20,7 @@ For example, with the URL `http://example.com/wp-json/wp/v2/posts/123`:
  	* `DELETE` triggers a `delete_item` method, returning the now-deleted post data to the client.
 
 [alert]
-On sites without pretty permalinks, the route is instead added to the URL as the `rest_route` parameter. For the above example, the full URL would then be `http://example.com/?rest_route=/wp/v2/posts/123`
+On sites without pretty permalinks, the route is instead added to the URL as the `rest_route` parameter. For the above example, the full URL would then be <code>http://example.com/?rest_route=/wp/v2/posts/123</code>
 [/alert]
 
 
@@ -73,7 +73,7 @@ The override parameter does not really solve our problem either, as both routes
 
 It is extremely important to add namespaces to your routes. The "core" endpoints use the `wp/v2` namespace.
 
-[warning]**Do not place anything into the `wp` namespace unless you are making endpoints with the intention of merging them into core.**[/warning]
+[warning]<strong>Do not place anything into the <code>wp</code> namespace unless you are making endpoints with the intention of merging them into core.</strong>[/warning]
 
 There are some key things to take notice of in the core endpoint namespace. The first part of the namespace is `wp`, which represents the vendor name; WordPress. For our plugins we will want to come up with unique names for what we call the vendor portion of the namespace. In the example above we used `hello-world`.
 
diff --git a/index.md b/index.md
@@ -2,7 +2,7 @@
 
 The WordPress REST API provides API endpoints for WordPress data types that allow developers to interact with sites remotely by sending and receiving [JSON](https://en.wikipedia.org/wiki/JSON) (JavaScript Object Notation) objects. JSON is an open standard data format that is lightweight and human-readable, and looks like Objects do in JavaScript; hence the name. When you send content to or make a request to the API, the response will be returned in JSON. This enables developers to create, read and update WordPress content from client-side JavaScript or from external applications, even those written in languages beyond PHP.
 
-[info]Looking for a list of the other APIs available within WordPress? You can find the [documentation here](https://codex.wordpress.org/WordPress_APIs).[/info]
+[info]Looking for a list of the other APIs available within WordPress? You can find the <a href="https://codex.wordpress.org/WordPress_APIs">documentation here</a>.[/info]
 
 
 ## Why use the WordPress REST API
diff --git a/using-the-rest-api/authentication.md b/using-the-rest-api/authentication.md
@@ -60,7 +60,7 @@ While cookie authentication is the only authentication mechanism available nativ
 
 [info]
 
-There's also a [Basic Authentication](https://github.com/WP-API/Basic-Auth) plugin.
+There's also a <a href="https://github.com/WP-API/Basic-Auth">Basic Authentication</a> plugin.
 
 Note that this plugin requires sending your username and password with every request, and should only be used for development and testing i.e. not in a production environment.
 
diff --git a/using-the-rest-api/client-libraries.md b/using-the-rest-api/client-libraries.md
@@ -4,7 +4,7 @@ The API can be used from any application by sending basic HTTP requests; however
 
 [alert]Aside from the Backbone.js client, these libraries are not part of WordPress core, and are not necessarily maintained or endorsed by the WordPress REST API team.[/alert]
 
-[info]To perform authenticated requests from outside of the WordPress admin, themes, or plugins, a separate [authentication plugin](https://developer.wordpress.org/rest-api/authentication/#authentication-plugins) is required.[/info]
+[info]To perform authenticated requests from outside of the WordPress admin, themes, or plugins, a separate <a href="https://developer.wordpress.org/rest-api/authentication/#authentication-plugins">authentication plugin</a> is required.[/info]
 
 
 ## JavaScript
diff --git a/using-the-rest-api/global-parameters.md b/using-the-rest-api/global-parameters.md
@@ -10,10 +10,11 @@ The API natively supports [JSONP](https://en.wikipedia.org/wiki/JSONP) responses
 The callback function can contain any alphanumeric, `_` (underscore), or `.` (period) character. Callbacks which contain invalid characters will receive a HTTP 400 error response, and the callback will not be called.
 
 [info]
-Modern browsers can use [Cross-Origin Resource Sharing (CORS)](https://en.wikipedia.org/wiki/Cross-origin_resource_sharing) preflight requests for cross-domain requests, but JSONP can be used to ensure support with all browsers.
+Modern browsers can use <a href="https://en.wikipedia.org/wiki/Cross-origin_resource_sharing">Cross-Origin Resource Sharing (CORS)</a> preflight requests for cross-domain requests, but JSONP can be used to ensure support with all browsers.
 
-* [Browser Support](http://caniuse.com/#feat=cors)
-* [MDN Article on CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS)
+<ul>
+  <li><a href="http://caniuse.com/#feat=cors">Browser Support</a></li>
+  <li><a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS">MDN Article on CORS</a></li>
 
 [/info]
 
diff --git a/using-the-rest-api/linking-and-embedding.md b/using-the-rest-api/linking-and-embedding.md
@@ -12,7 +12,7 @@ The links are an object containing a `href` property with an absolute URL to the
 For collection responses (those that return a list of objects rather than a top-level object), each item contains links, and the top-level response includes links via the `Link` header instead.
 
 [info]
-If your client library does not allow accessing headers, you can use the [`_envelope`](https://developer.wordpress.org/rest-api/global-parameters/#envelope) parameter to include the headers as body data instead.
+If your client library does not allow accessing headers, you can use the <a href="https://developer.wordpress.org/rest-api/global-parameters/#envelope"><code>_envelope</code></a> parameter to include the headers as body data instead.
 [/info]
 
 
diff --git a/using-the-rest-api/pagination.md b/using-the-rest-api/pagination.md
@@ -19,7 +19,7 @@ Any API response which contains multiple resources supports several common query
  	* `?per_page=5&amp;page=4` is equivalent to `?per_page=5&amp;offset=15`
 
 [tip]
-Large queries can hurt site performance, so `per_page` is **capped at 100 records**. If you wish to retrieve more than 100 records, for example to build a client-side list of all available categories, you may make multiple API requests and combine the results within your application.
+Large queries can hurt site performance, so <code>per_page</code> is <strong>capped at 100 records</strong>. If you wish to retrieve more than 100 records, for example to build a client-side list of all available categories, you may make multiple API requests and combine the results within your application.
 [/tip]
 
 To determine how many pages of data are available, the API returns two header fields with every paginated response:
