Fix links to 'deprecations' section

jasonrudolph · jasonrudolph · commit 21768228edd8 · 2013-11-06T09:34:59.000-05:00
diff --git a/content/changes/2013-04-25-deprecating-merge-commit-sha.html b/content/changes/2013-04-25-deprecating-merge-commit-sha.html
@@ -16,7 +16,7 @@
 attribute](/v3/pulls/#mergability) for improved understanding.
 
 To protect future API consumers from this confusion, we have
-[deprecated](/#deprecations) the `merge_commit_sha` attribute, and we will
+[deprecated](/v3/#deprecations) the `merge_commit_sha` attribute, and we will
 remove it in the next major version of the API.
 
 As always, if you have any questions or feedback, please drop us a line at
diff --git a/content/v3/media.md b/content/v3/media.md
@@ -137,4 +137,4 @@ The Commit, Commit Comparison, and Pull Request resources support
 [git-diff]: http://git-scm.com/docs/git-diff
 [git-patch]: http://git-scm.com/docs/git-format-patch
 [hypermedia]: /v3/#hypermedia
-[expected-changes]: /#deprecations
+[expected-changes]: /v3/#deprecations
diff --git a/content/v3/pulls.md b/content/v3/pulls.md
@@ -72,7 +72,7 @@ Each time the pull request receives new commits, GitHub creates a merge commit
 to _test_ whether the pull request can be automatically merged into the base
 branch. (This _test_ commit is not added to the base branch or the head branch.)
 The `merge_commit_sha` attribute holds the SHA of the _test_ merge commit;
-however, this attribute is [deprecated](/#deprecations) and is scheduled for
+however, this attribute is [deprecated](/v3/#deprecations) and is scheduled for
 removal in the next version of the API. The Boolean `mergeable` attribute will
 remain to indicate whether the pull request can be automatically merged.
 
diff --git a/content/v3/rate_limit.md b/content/v3/rate_limit.md
@@ -43,7 +43,7 @@ all the _rest_ of the API.
 #### Deprecation Notice
 
 The `"rate"` hash (shown at the bottom of the response above) is
-[deprecated](/#deprecations) and is scheduled for removal in the next
+[deprecated](/v3/#deprecations) and is scheduled for removal in the next
 version of the API.
 
 If you're writing new API client code (or updating your existing code), you
diff --git a/content/v3/search/legacy.md b/content/v3/search/legacy.md
@@ -14,7 +14,7 @@ v3. There should be no changes, other than the new URL and JSON output format.
 
 <div class="alert">
   <p>
-    The Legacy Search API (described below) is <a href="/#deprecations">deprecated</a>
+    The Legacy Search API (described below) is <a href="/v3/#deprecations">deprecated</a>
     and is scheduled for removal in the next version of the API.
 
     We recommend using the <a href="/v3/search/">v3 Search API</a> instead.

-Original file line number
+Diff line change
 <div class="alert">
   <p>
 -    The Legacy Search API (described below) is <a href="https://github.com/#deprecations">deprecated</a>
 +    The Legacy Search API (described below) is <a href="https://github.com/v3/#deprecations">deprecated</a>
     and is scheduled for removal in the next version of the API.
     We recommend using the <a href="/v3/search/">v3 Search API</a> instead.