Correct links in definitions (#36834)

content/apps/oauth-apps/building-oauth-apps/authenticating-to-the-rest-api-with-an-oauth-app.md

@@ -359,13 +359,13 @@ the same callback URL, we've got to do a little bit of wonkiness to make it work
 Also, if we had never authorized this application to access our {% data variables.product.product_name %} data,
 we would've seen the same confirmation dialog from earlier pop-up and warn us.
 
-[webflow]: /apps/building-oauth-apps/authorizing-oauth-apps/
+[webflow]: /apps/oauth-apps/building-oauth-apps/authorizing-oauth-apps
 [Sinatra]: http://www.sinatrarb.com/
 [about env vars]: http://en.wikipedia.org/wiki/Environment_variable#Getting_and_setting_environment_variables
 [Sinatra guide]: https://github.com/sinatra/sinatra-book/blob/master/book/Introduction.markdown#hello-world-application
 [REST Client]: https://github.com/archiloque/rest-client
-[libraries]: /libraries/
-[oauth scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/
+[libraries]: /rest/overview/libraries
+[oauth scopes]: /apps/oauth-apps/building-oauth-apps/scopes-for-oauth-apps
 [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/basics-of-authentication
 [new oauth app]: https://github.com/settings/applications/new
 [app settings]: https://github.com/settings/developers

content/authentication/connecting-to-github-with-ssh/using-ssh-agent-forwarding.md

@@ -164,6 +164,6 @@ For MacOS versions prior to Monterey (12.0), use `-K` instead of `--apple-use-ke
 {% endtip %}
 
 [tech-tips]: http://www.unixwiz.net/techtips/ssh-agent-forwarding.html
-[generating-keys]: /articles/generating-ssh-keys
-[ssh-passphrases]: /ssh-key-passphrases/
-[autolaunch-ssh-agent]: /github/authenticating-to-github/working-with-ssh-key-passphrases#auto-launching-ssh-agent-on-git-for-windows
+[generating-keys]: /authentication/connecting-to-github-with-ssh
+[ssh-passphrases]: /authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases
+[autolaunch-ssh-agent]: /authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases#auto-launching-ssh-agent-on-git-for-windows

content/rest/guides/best-practices-for-integrators.md

@@ -170,4 +170,4 @@ Rather than ignore repeated `4xx` and `5xx` status codes, you should ensure that
 
 Intentionally ignoring repeated validation errors may result in the suspension of your app for abuse.
 
-[event-types]: /webhooks/event-payloads
+[event-types]: /webhooks-and-events/webhooks/webhook-events-and-payloads

content/rest/guides/delivering-deployments.md

@@ -189,15 +189,15 @@ server we've built above:
 That's it! You don't need to build your own deployment setup to use this example.
 You can always rely on [GitHub integrations][integrations].
 
-[deploy API]: /rest/reference/repos#deployments
-[status API]: /guides/building-a-ci-server
+[deploy API]: /rest/repos#deployments
+[status API]: /rest/guides/building-a-ci-server
 [ngrok]: https://ngrok.com/
-[using ngrok]: /webhooks/configuring/#using-ngrok
+[using ngrok]: /webhooks-and-events/webhooks/configuring-your-server-to-receive-payloads#using-ngrok
 [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/delivering-deployments
 [Sinatra]: http://www.sinatrarb.com/
-[webhook]: /webhooks/
+[webhook]: /webhooks-and-events/webhooks/about-webhooks
 [octokit.rb]: https://github.com/octokit/octokit.rb
-[access token]: /articles/creating-an-access-token-for-command-line-use
+[access token]: /authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token
 [travis api]: https://api.travis-ci.com/docs/
 [janky]: https://github.com/github/janky
 [heaven]: https://github.com/atmos/heaven

content/rest/guides/working-with-comments.md

@@ -122,8 +122,8 @@ on the entire commit.
 [commit comment]: https://github.com/octocat/Spoon-Knife/commit/cbc28e7c8caee26febc8c013b0adfb97a4edd96e#commitcomment-4049848
 [sample PR]: https://github.com/octocat/Spoon-Knife/pull/1176
 [platform-samples]: https://github.com/github/platform-samples/tree/master/api/ruby/working-with-comments
-[issues]: /rest/reference/issues#comments
-[personal token]: /articles/creating-an-access-token-for-command-line-use
+[issues]: /rest/issues#comments
+[personal token]: /authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token
 [octokit.rb]: https://github.com/octokit/octokit.rb
-[PR Review API]: /rest/reference/pulls#comments
-[commit comment API]: /rest/reference/commits#get-a-commit-comment
+[PR Review API]: /rest/pulls#comments
+[commit comment API]: /rest/commits#get-a-commit-comment

content/webhooks-and-events/webhooks/about-webhooks.md

@@ -36,5 +36,5 @@ For a complete list of available webhook events and their payloads, see "[AUTOTI
 
 For more information about the `ping` event webhook payload, see the [`ping`](/webhooks-and-events/webhooks/webhook-events-and-payloads#ping) event.
 
-[org-hooks]: /rest/reference/orgs#webhooks/
-[repo-hooks]: /rest/reference/repos#webhooks
+[org-hooks]: /rest/orgs#webhooks/
+[repo-hooks]: /rest/repos#webhooks

content/webhooks-and-events/webhooks/creating-webhooks.md

@@ -94,6 +94,6 @@ Now that you've created the webhook, it's time to set up our local server to tes
 
 To configure a webhook for all events, use the wildcard (`*`) character to specify the webhook events. When you add the wildcard event, we'll replace any existing events you have configured with the wildcard event and send you payloads for all supported events. You'll also automatically get any new events we might add in the future.
 
-[webhooks-overview]: /webhooks/
-[webhook-api]: /rest/reference/repos#hooks
-[hooks-api]: /webhooks/#events
+[webhooks-overview]: /webhooks-and-events/webhooks/about-webhooks
+[webhook-api]: /rest/repos#hooks
+[hooks-api]: /webhooks-and-events/webhooks/about-webhooks#events