Get rid of options without breaking everything

Author: mthurman

Rules

@@ -29,7 +29,7 @@ compile '*' do
     # don’t filter binary items
   else
     filter :erb
-    filter :kramdown, :toc_levels => [2], :enable_coderay => false
+    filter :kramdown, :toc_levels => [2], :enable_coderay => false, :parse_block_html => true
     filter :colorize_syntax, :default_colorizer => :pygmentsrb, :linenos => 'inline'
     layout 'default'
   end

content/reference/authentication/index.md

@@ -25,9 +25,8 @@ It should go without saying, but for the sake of user privacy and security, plea
 
 You authenticate to our API by use of an **access token**. There are two types of access tokens: _app_ tokens and _user_ tokens. **App tokens** (referred to as "client tokens" in the [OAuth 2.0 standard](http://tools.ietf.org/html/rfc6749)) represent access to API resources on behalf of the application and **user tokens** represent access to API resources on behalf of a specific user. Some resources are only accessible to app or user tokens.
 
-{::options parse_block_html="true" /}
 <div class="alert alert-info alert-block">
-**Note:** Only Apps created by a developer account can request access tokens for other App.net users. If you do not have a developer account, then your app can only be used with your own account. If you ever downgrade your developer account, all current tokens for your app will still work but no new users will be able to authorize it.
+<p>Only Apps created by a developer account can request access tokens for other App.net users. If you do not have a developer account, then your app can only be used with your own account. If you ever downgrade your developer account, all current tokens for your app will still work but no new users will be able to authorize it.</p>
 </div>
 
 ## What kind of token do I need?

content/reference/make-request/migrations.md

@@ -9,8 +9,6 @@ title: "Migrations"
 
 We reserve the right to make incremental changes to the API as we deem necessary. In order to make it possible to change the API but still support legacy applications, we will make use of migrations. Migrations are a per-app feature that developers may toggle for their own apps from the time that the old behavior is deprecated until the time that it has reached the end of its life (EOL). Once the EOL date is reached, the migration will be enabled for all apps with no legacy mode available.
 
-{::options parse_block_html="true" /}
-
 ## Accessing Migration Data
 
 We offer a single toggle for each migration and app that will globally turn the migration on (current mode) or off (legacy mode) for that app as well as a per-call header mechanism that overrides the global behavior.

content/reference/make-request/responses.md

@@ -11,8 +11,6 @@ All responses to requests to the App.net API endpoints listed under [Resources](
 
 *Please note: the [authentication endpoints](/reference/authentication) return a slightly different format that follows the OAuth2 specification.*
 
-{::options parse_block_html="true" /}
-
 ## Response Envelope
 
 The top-level response is an object containing two keys. The first key, `data`, corresponds to the actual response item requested. This may either be an object itself or a list of objects. The particular data returned is described in each endpoint's documentation. If the request is unsuccessful (results in an error), no `data` key will be present.

content/reference/resources/place/index.md

@@ -162,9 +162,10 @@ Performs a search for nearest places from given latitude and longitude. Optional
 
 Returns a list of Places sorted by distance or distance/string match if `q` is provided. These are the same Place objects as returned by the previous endpoint but will also include a `distance` property which gives, in meters, the distance from the search centroid to the Place.
 
-{::options parse_block_html="true" /}
 <div class="alert alert-error alert-block">
-**When using this endpoint, it is a requirement that _all_ requests originate from user actions.** As an example, acceptable use cases include when a user presses a button to search for local Places or when a user types a character to specify part of a Place name. Unacceptable use cases include automated access (e.g. "bots", "scrapers"), periodic scans and attempts to create comprehensive local caches or copies of the Place data. **We will be monitoring search usage and will take necessary actions to terminate unacceptable use.**
+<p>When using this endpoint, it is a requirement that <em>all</em> requests originate from user actions. As an example, acceptable use cases include when a user presses a button to search for local Places or when a user types a character to specify part of a Place name. Unacceptable use cases include automated access (e.g. "bots", "scrapers"), periodic scans and attempts to create comprehensive local caches or copies of the Place data.</p>
+
+<p>We will be monitoring search usage and will take necessary actions to terminate unacceptable use.</p>
 </div>
 
 <%= endpoint "GET", "places/search", "User" %>

layouts/partials/object-tab.html

@@ -3,5 +3,4 @@
     <li><a href="#endpoints" data-toggle="tab">Endpoints</a></li>
 </ul>
 
-{::options parse_block_html="true" /}
-<div id="my-tab-content" class="tab-content"><div class="tab-pane active" id="object">
+<div id="my-tab-content" class="tab-content"><div class="tab-pane active" id="object">