Fixed Broken Links

content/en/docs/onboarding/01-starting-out.md

@@ -54,19 +54,19 @@ The Kubernetes community adheres to the following principles:
 * Inclusive is better than exclusive
 * Evolution is better than stagnation
 
-[Read more about our community values.](/community/values/)
+[Read more about our community values.](https://github.com/kubernetes/community/blob/master/values.md)
 
 ---
 
 # What behavior is expected of contributors?
 
 The Kubernetes community strives to be safe, respectful and inclusive. We expect all contributors to:
 
-* Abide by the [CNCF Code of Conduct](/community/code-of-conduct/)
+* Abide by the [CNCF Code of Conduct](https://github.com/kubernetes/community/blob/master/code-of-conduct.md)
 * Help foster an open and welcoming community
 * Respect their fellow contributors.
 
-[Learn more about the Kubernetes community values.](/community/values/)
+[Learn more about the Kubernetes community values.](https://github.com/kubernetes/community/blob/master/values.md)
 
 ---
 
@@ -84,7 +84,7 @@ The Code of Conduct serves as a set of rules used by the Kubernetes community to
 
 The Code of Conduct Committee oversees and handles all incidents and responses regarding code of conduct issues and violations.
 
-* [Read about the committee's reporting and response process.](/community/code-of-conduct-incident-process/)
+* [Read about the committee's reporting and response process.](https://github.com/kubernetes/community/blob/master/committee-code-of-conduct/incident-process.md)
 
 ---
 
@@ -129,9 +129,9 @@ Some topics, such as Security or Code of Conduct, require discretion. Committees
 
 # Where can I learn more?
 
-The [Kubernetes Community Resources page](/community/) has links to documents that describe our community structure and governance.
+The [Kubernetes Community Resources page](https://github.com/kubernetes/community/tree/62e4d0e54af58c2fc7ca39b7a885e13f30ffe452) has links to documents that describe our community structure and governance.
 
-* [The Community Groups page](/community/community-groups/) lists all current SIGs, working groups, and committees.
+* [The Community Groups page](https://github.com/kubernetes/community/blob/62e4d0e54af58c2fc7ca39b7a885e13f30ffe452/sig-list.md) lists all current SIGs, working groups, and committees.
 * [The governance document](https://github.com/kubernetes/community/blob/master/governance.md) drills down into more of the specifics.
 
 <div class="bottom-nav">

content/en/docs/onboarding/03-pull-requests.md

@@ -49,7 +49,7 @@ You’ll want to review the basic pull request process you learned at the end of
 
 * Every pull request [starts with a branch on your fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository) of a Kubernetes project.
 * You can create pull requests using the GitHub website, any of the GitHub tools, or some third-party GitHub interfaces.
-* Take time to review the [GitHub Workflow documentation](/docs/guide/github-workflow/).
+* Take time to review the [GitHub Workflow documentation](https://github.com/kubernetes/community/blob/62e4d0e54af58c2fc7ca39b7a885e13f30ffe452/contributors/guide/github-workflow.md).
 
 ---
 
@@ -59,7 +59,7 @@ Kubernetes generally follows the standard GitHub pull request process, but there
 
 * Right away, a bot starts adding automated labels to your PR.
 * The bot helps you facilitate PR review. You can use [these commands to interact with the bot](https://prow.k8s.io/command-help).
-* [You can learn more about the Kubernetes pull request process here.](/docs/guide/pull-requests/)
+* [You can learn more about the Kubernetes pull request process here.](https://github.com/kubernetes/community/blob/62e4d0e54af58c2fc7ca39b7a885e13f30ffe452/contributors/guide/pull-requests.md)
 
 ---
 
@@ -71,24 +71,24 @@ Kubernetes generally follows the standard GitHub pull request process, but there
     * Content
     * Potential website changes
 
-You can respond to comments from reviewers through comments or additional changes that you push to your development branch. [We will cover code review in a later unit.](../07-code-review)
+You can respond to comments from reviewers through comments or additional changes that you push to your development branch. [We will cover code review in a later unit.](https://github.com/kubernetes/contributor-site/blob/master/content/en/docs/onboarding/07-code-review.md)
 
 ---
 
 ## When are my pull requests run through tests?
 
 * A bot runs your PR through a few pre-commit tests automatically.
 * The results of these tests will be posted to your pull request’s discussion automatically.
-* Once a reviewer adds the **ok-to-test** label, [the bot will run your changes through end-to-end (e2e) tests](/docs/guide/pull-requests/#how-the-e2e-tests-work).
+* Once a reviewer adds the **ok-to-test** label, [the bot will run your changes through end-to-end (e2e) tests](https://github.com/kubernetes/community/blob/62e4d0e54af58c2fc7ca39b7a885e13f30ffe452/contributors/guide/pull-requests.md#how-the-e2e-tests-work).
 
 ---
 
 ## What do I do if my test fails?
 
 * The test results should give some indication of what went wrong.
-* Make changes, push them to your branch, and [continue iterating through the pull request process](/docs/guide/pull-requests/).
+* Make changes, push them to your branch, and [continue iterating through the pull request process](https://github.com/kubernetes/community/blob/62e4d0e54af58c2fc7ca39b7a885e13f30ffe452/contributors/guide/pull-requests.md).
 
-We will cover tests in more detail [in a later unit](../06-testing/).
+We will cover tests in more detail [in a later unit](https://github.com/kubernetes/contributor-site/blob/master/content/en/docs/onboarding/06-testing.md).
 
 <div class="bottom-nav">
     <a href="/docs/onboarding">Onboarding Index</a> | <a href="../04-issues-management/">Next Section</a>

content/en/docs/onboarding/04-issues-management.md

@@ -122,7 +122,7 @@ That list of labels is really long, but you won't need to worry about most of th
 * Triage can happen asynchronously and continuously, or in regularly scheduled meetings. 
 * Each SIG may have its own approach to triaging.
 
-Triaging is critical for keeping track of new issues, bugs, and problems. [Read the Issue Triage Guidelines for more information.](/docs/guide/issue-triage/)
+Triaging is critical for keeping track of new issues, bugs, and problems. [Read the Issue Triage Guidelines for more information.](https://github.com/kubernetes/community/blob/62e4d0e54af58c2fc7ca39b7a885e13f30ffe452/contributors/guide/issue-triage.md)
 
 ---
 

content/en/docs/onboarding/06-testing.md

@@ -122,7 +122,7 @@ You should run tests locally or in your development environment before submittin
 * When the tests fail, your pull request will stall.
 * You will need to use the **/ok-to-test** command to tell the bot to run tests again.
 
-[Read about the ok-to-test label in the Pull Request Process documentation.](/docs/guide/pull-requests/#more-about-ok-to-test)
+[Read about the ok-to-test label in the Pull Request Process documentation.](https://github.com/kubernetes/community/blob/62e4d0e54af58c2fc7ca39b7a885e13f30ffe452/contributors/guide/pull-requests.md)
 
 ---
 
@@ -135,7 +135,7 @@ We've covered a lot of ground in this unit, and if you want to go deeper, here i
 * [The Testing Guide](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-testing/testing.md#unit-tests)
 * [Integration Testing in Kubernetes](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-testing/integration-tests.md)
 * [End-to-End Testing Guide](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-testing/e2e-tests.md)
-* [Pull Request documentation](/docs/guide/pull-requests/#more-about-ok-to-test)
+* [Pull Request documentation](https://github.com/kubernetes/community/blob/62e4d0e54af58c2fc7ca39b7a885e13f30ffe452/contributors/guide/pull-requests.md)
 
 <div class="bottom-nav">
     <a href="/docs/onboarding">Onboarding Index</a> | <a href="../07-code-review/">Next Section</a>

content/en/docs/onboarding/08-community.md

@@ -92,7 +92,7 @@ The Kubernetes Slack server has over 500 channels!
 Each SIG and Working Group has its favored method of communication. You can start in their Slack channel and ask around.
 
 * By working with a SIG, you will learn how its members communicate.
-* [The Community Groups list](/community/community-groups/) is a great place to learn about communication preferences.
+* [The Community Groups list](https://github.com/kubernetes/community/blob/62e4d0e54af58c2fc7ca39b7a885e13f30ffe452/sig-list.md) is a great place to learn about communication preferences.
     * This is also where you will learn about each group’s regularly scheduled meetings and how to attend.
 
 ---
@@ -119,7 +119,7 @@ While KubeCon is organized by the [Cloud Native Computing Foundation (CNCF)](htt
 
 We have extensive guidelines and policies around our various communication channels.
 
-* [Read the Kubernetes Communication Platform Guidelines and Policies.](/docs/comms/)
+* [Read the Kubernetes Communication Platform Guidelines and Policies.](https://github.com/kubernetes/contributor-site/blob/fc260cf10a5d736e2941a854fd1fab8f66f068a3/content/en/docs/comms/_index.md)
 
 <div class="bottom-nav">
     <a href="/docs/onboarding">Onboarding Index</a> | <a href="../09-documentation/">Next Section</a>

content/en/docs/onboarding/09-documentation.md

@@ -46,7 +46,7 @@ The user-facing documentation deals with how to install, configure, and operate
 
 The [community documentation](https://www.kubernetes.dev/) is an informal collection of docs maintained by contributors. It consists of:
 
-* [The Contributor Guide](/docs/)
+* [The Contributor Guide](https://github.com/kubernetes/community/tree/62e4d0e54af58c2fc7ca39b7a885e13f30ffe452/contributors/guide)
 * [The Developer Guide](https://github.com/kubernetes/community/tree/master/contributors/devel/)
 * [The Community website](https://www.kubernetes.dev/)