'Note:' is almost always redundant

mthurman · mthurman · commit 7ba49bf855f3 · 2014-04-02T17:49:13.000-07:00
diff --git a/content/reference/authentication/flows/app-access-token.md b/content/reference/authentication/flows/app-access-token.md
@@ -19,7 +19,7 @@ with URL-encoded POST body:
         &client_secret=[your client secret]
         &grant_type=client_credentials
 
-> Note: we also accept the `client_id` and `client_secret` parameters via the Authorization header, as described in [section 2.3.1 of the spec](http://tools.ietf.org/html/rfc6749#section-2.3.1).
+> We also accept the `client_id` and `client_secret` parameters via the Authorization header, as described in [section 2.3.1 of the OAuth 2 spec](http://tools.ietf.org/html/rfc6749#section-2.3.1).
 
 App.net will respond with a JSON-encoded token:
 
diff --git a/content/reference/authentication/flows/web.md b/content/reference/authentication/flows/web.md
@@ -45,7 +45,7 @@ Your `redirect_uri` must be registered with App.net before you can use it.
         &redirect_uri=[your registered redirect URI]
         &code=[code received from redirect URI]
 
-    > Note: we also accept the `client_id` and `client_secret` parameters via the Authorization header, as described in [section 2.3.1 of the spec](http://tools.ietf.org/html/rfc6749#section-2.3.1).
+    > We also accept the `client_id` and `client_secret` parameters via the Authorization header, as described in [section 2.3.1 of the OAuth 2 spec](http://tools.ietf.org/html/rfc6749#section-2.3.1).
 
 1. App.net will respond with a JSON-encoded token: `{"access_token": "[user access token]", "token": {...Token object...}}`
 
diff --git a/content/reference/authentication/index.md b/content/reference/authentication/index.md
@@ -137,7 +137,7 @@ When making a call to one of our API resources, there are three ways to include
 
 * Add `access_token` to HTTP body. 
 
-    > Note: this method will only work with the `PUT`, `POST`, and `PATCH` methods. `GET` and `DELETE` do not accept an HTTP body.
+    > This method will only work with the `PUT`, `POST`, and `PATCH` methods. `GET` and `DELETE` do not accept an HTTP body.
 
     <%= curl_example(:post, "posts", :none, {
         :data => {"text" => "Test post", "access_token" => "<YOUR ACCESS TOKEN>"},
diff --git a/content/reference/make-request/responses.md b/content/reference/make-request/responses.md
@@ -9,7 +9,7 @@ title: "Responses"
 
 All responses to requests to the App.net API endpoints listed under [Resources](/reference/resources/), whether successful or not, will be returned in the same type of envelope structure. This document describes how that envelope works and what it may contain.
 
-*Please note: the [authentication endpoints](/reference/authentication) return a slightly different format that follows the OAuth2 specification.*
+*The [authentication endpoints](/reference/authentication) return a slightly different format that follows the OAuth2 specification.*
 
 ## Response Envelope
 
@@ -63,7 +63,7 @@ To request pretty-printing, send the following HTTP header with your request:
 
     X-ADN-Pretty-JSON: 1
 
-*Note: Sending any value is sufficient. Omit the header entirely if you wish to receive minified JSON.*
+Sending any value is sufficient. Omit the header entirely if you wish to receive minified JSON.
 
 ## Error Conditions
 
diff --git a/content/reference/meta/entities.md b/content/reference/meta/entities.md
@@ -13,7 +13,7 @@ Usually entities are extracted from the Post text by App.net's servers. We allow
 
 Ranges specified by entities may be adjacent, but may not overlap.
 
-<div class="alert alert-info"><b>Note:</b> <code>pos</code> and <code>len</code> fields are given as UTF-32 code points. Many string implementations (in particular, Cocoa's NSString class and Javascript's strings) use UTF-16 or UCS-2 encoding internally, and thus the indices given will not map directly to UTF-16 code points if encoded with surrogate pairs, e.g., emoji characters.</div>
+<div class="alert alert-info"><code>pos</code> and <code>len</code> fields are given as UTF-32 code points. Many string implementations (in particular, Cocoa's NSString class and Javascript's strings) use UTF-16 or UCS-2 encoding internally, and thus the indices given will not map directly to UTF-16 code points if encoded with surrogate pairs, e.g., emoji characters.</div>
 
 All of the following examples are about the following text:
 
diff --git a/content/reference/other/feeds.md b/content/reference/other/feeds.md
@@ -18,7 +18,7 @@ There are 2 different kinds of feeds, but they all follow the same pattern:
 
 We intend to support more feed formats and richer support for filters in the near future.
 
-*Note:* While the URLs are similar to other API URLs feeds, they are under a different root.
+While the URLs are similar to other API URLs feeds, they are under a different root.
 
 ## Filters
 
diff --git a/content/reference/other/web-intents.md b/content/reference/other/web-intents.md
@@ -11,7 +11,7 @@ Web intents are an easy way to integrate with App.net; you don't even need to us
 
 
 <div class="alert alert-info alert-block">
-    <p><strong>Note:</strong> If you just want a simple follow or share button you can use <a href='http://app.net/about/buttons/'>button builder</a> instead. We've also open sourced the buttons so that you could host them your self. Checkout the <a href="https://github.com/appdotnet/piha">github repo</a> for more information on how to do that.</p>
+    <p>If you just want a simple follow or share button you can use <a href='http://app.net/about/buttons/'>button builder</a> instead. We've also open sourced the buttons so that you could host them your self. Checkout the <a href="https://github.com/appdotnet/piha">github repo</a> for more information on how to do that.</p>
 </div>
 
 ## The Post Intent
diff --git a/content/reference/resources/file/index.md b/content/reference/resources/file/index.md
@@ -200,7 +200,7 @@ Derived files will include the keys shown in the example below. Please see [the
 
 ### Auto-generated derived files
 
-For some files, App.net will auto generate derived files. *Note: any new auto-generated derived file keys will be prefixed with `core_`.*
+For some files, App.net will auto generate derived files. *Any new auto-generated derived file keys will be prefixed with `core_`.*
 
 * `image_thumb_200s`: When the root file is an image, App.net will generate a 200x200 square thumbnail of the image that shrinks and crops the center square of the image.
 * `image_thumb_960r`: When the root file is an image, App.net will scale down the entire image so it fits within a 640x960 pixel bounding box. This thumbnail will not be cropped.
diff --git a/content/reference/resources/interaction/index.md b/content/reference/resources/interaction/index.md
@@ -9,7 +9,7 @@ title: "Interactions"
 
 Interactions are objects that represent users taking certain actions on App.net. Interactions are structured to form a sentence like: User X took action Y on object Z. If multiple users take the same action (e.g. multiple users reply to one post) within a set time window those events will be combined into a single Interaction.
 
-> Note: the `objects` list of an Interaction will vary based on the `action`
+> The `objects` list of an Interaction will vary based on the `action`
 
 (Example) @dalton and @berg reposted post 1:
 
@@ -59,10 +59,10 @@ List all the [Interactions](/reference/resources/interaction/) other users have
 
 <%= pagination_note %>
 
-> Note: you can only request this list for the current user.
+> You can only request this list for the current user.
 
 <!-- blockquote break -->
-> Note: although this endpoint supports paging, a user's Interactions stream is continuously rebuilt as new actions in the system occur, so developers should generally plan to refetch the stream whenever switching to display it as Interactions may have shifted their position, with users being added or removed. If you need to keep track of activity in a more precise manner, you should using the [Streaming API](/reference/resources/app-stream/) to monitor the global feed for relevant activity.
+> Although this endpoint supports paging, a user's Interactions stream is continuously rebuilt as new actions in the system occur, so developers should generally plan to refetch the stream whenever switching to display it as Interactions may have shifted their position, with users being added or removed. If you need to keep track of activity in a more precise manner, you should using the [Streaming API](/reference/resources/app-stream/) to monitor the global feed for relevant activity.
 
 This endpoint accepts the `interaction_actions` as a query string parameter whose value is a comma separated list of actions you're interested in. For instance, if you're only interested in repost and follow interactions you could request `stream/0/users/me/interactions?interaction_actions=repost,follow`.
 
diff --git a/content/reference/resources/message/lifecycle.md b/content/reference/resources/message/lifecycle.md
@@ -52,7 +52,7 @@ end %>
 
 Delete a message. The current user must be the same user who created the Message. It returns the deleted Message on success.
 
-*Note: you can always delete a message you created even if you are no longer able to view the rest of the Channel anymore.*
+*You can always delete a message you created even if you are no longer able to view the rest of the Channel anymore.*
 
 *Remember, access tokens can not be passed in a HTTP body for `DELETE` requests. Please refer to the [authentication documentation](/reference/authentication/#making-authenticated-api-requests).*
 
diff --git a/content/reference/resources/message/lookup.md b/content/reference/resources/message/lookup.md
@@ -11,7 +11,7 @@ title: "Message Lookup"
 
 Returns a specific [Message](/reference/resources/message/).
 
-*Note: you can always retrieve a message you created even if you are no longer able to view the rest of the Channel anymore.*
+*You can always retrieve a message you created even if you are no longer able to view the rest of the Channel anymore.*
 
 <%= general_params_note_for "message" %>
 
diff --git a/content/reference/resources/post/lifecycle.md b/content/reference/resources/post/lifecycle.md
@@ -15,7 +15,7 @@ You can also create a Post by sending JSON in the HTTP post body that matches th
 
 If you want to test how your text will be processed you can use the [text processor](/reference/resources/text-processor).
 
-*Note: You cannot reply to a repost. Please reply to the parent Post.*
+*You cannot reply to a repost. Please reply to the parent Post.*
 
 <%= general_params_note_for "post" %>
 
diff --git a/content/reference/resources/post/reposts.md b/content/reference/resources/post/reposts.md
@@ -33,7 +33,7 @@ end %>
 
 ## Unrepost a Post
 
-Given the original `post_id`, delete the current user's repost. *Note: this same functionality can be accomplished by [deleting using the repost's post_id](/reference/resources/post/lifecycle/#delete-a-post)*.
+Given the original `post_id`, delete the current user's repost. *This same functionality can be accomplished by [deleting using the repost's post_id](/reference/resources/post/lifecycle/#delete-a-post)*.
 
 <%= general_params_note_for "post" %>
 
diff --git a/content/reference/resources/post/stars.md b/content/reference/resources/post/stars.md
@@ -11,7 +11,7 @@ title: "Stars"
 
 Save a given Post to the current User's stars. This is just a "save" action, not a sharing action. A User's stars are visible to others, but they are not automatically added to your followers' streams.
 
-*Note: A repost cannot be starred. Please star the parent Post.*
+*A repost cannot be starred. Please star the parent Post.*
 
 <%= general_params_note_for "post" %>
 
diff --git a/content/reference/resources/user/muting.md b/content/reference/resources/user/muting.md
@@ -9,7 +9,7 @@ title: "User Muting"
 
 ## Mute a User
 
-Hide all posts for a User in all streams. *Note: if you still explicitly request this User's stream or a Post from this User, it will not be hidden.*
+Hide all posts for a User in all streams. *If you still explicitly request this User's stream or a Post from this User, it will not be hidden.*
 
 <%= general_params_note_for "user" %>
 
diff --git a/lib/helpers.rb b/lib/helpers.rb
@@ -15,7 +15,7 @@ def migration_warning(migrations = [])
             plur = ""
         end
 
-        "<div class=\"alert alert-info\"><b>Note:</b> This endpoint is currently migrated by the <code>#{ join_all migrations }</code> migration#{ plur  }. Please refer to the <a href=\"/reference/make-request/migrations/#current-migrations\">Migrations documentation</a> for more info.</div>"
+        "<div class=\"alert alert-info\">This endpoint is currently migrated by the <code>#{ join_all migrations }</code> migration#{ plur  }. Please refer to the <a href=\"/reference/make-request/migrations/#current-migrations\">Migrations documentation</a> for more info.</div>"
     end
 end
 
