[yunikorn-site] branch master updated: [YUNIKORN-1380] Multiple page URLs broken for website (#224)

[cc...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

ccondit pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/yunikorn-site.git


The following commit(s) were added to refs/heads/master by this push:
     new 2ea460266 [YUNIKORN-1380] Multiple page URLs broken for website (#224)
2ea460266 is described below

commit 2ea46026606fd26cc26bdc70c0c857ab4151db16
Author: Jagadeesan A S <ja...@gmail.com>
AuthorDate: Tue Dec 13 10:09:05 2022 -0600

    [YUNIKORN-1380] Multiple page URLs broken for website (#224)
    
    Closes: #224
    
    Signed-off-by: Craig Condit <cc...@apache.org>
---
 src/pages/community/get_involved.md      | 4 ++--
 src/pages/community/how_to_contribute.md | 6 +++---
 src/pages/community/reporting_issues.md  | 2 +-
 3 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/src/pages/community/get_involved.md b/src/pages/community/get_involved.md
index 8c0b92c1b..76b0ef14c 100644
--- a/src/pages/community/get_involved.md
+++ b/src/pages/community/get_involved.md
@@ -34,7 +34,7 @@ importance of this diversity and the value of "The Apache Way".  We welcome any
 Please join us through one of the following channels:
 
 ### Contribute through github
-- Basic steps of contributing to project is explained here - [How to contribute](how_to_contribute)
+- Basic steps of contributing to project is explained here - [How to contribute](/community/how_to_contribute)
 
 ### Communication Channels
 
@@ -81,7 +81,7 @@ import TabItem from '@theme/TabItem';
 We welcome you to try our latest releases and share your experiences.
 
 Any point, if you are facing any issues:
-- Raise an issue or a feedback in the JIRA as per our [guide](reporting_issues).
+- Raise an issue or a feedback in the JIRA as per our [guide](/community/reporting_issues).
 - Clarify / Seek help in the YuniKorn slack `#yunikorn-user` channel
 
 ### Other feedback mechanisms
diff --git a/src/pages/community/how_to_contribute.md b/src/pages/community/how_to_contribute.md
index 032329970..aa561643f 100644
--- a/src/pages/community/how_to_contribute.md
+++ b/src/pages/community/how_to_contribute.md
@@ -51,7 +51,7 @@ Don't share the above information in a channel on slack, reach out on a channel
 ## Find an issue
 We use JIRA issues to track bugs for this project.
 Find an issue that you would like to work on, or file a new one if you have discovered a new issue.
-For help with reporting issues look at the [how to report an issue](reporting_issues).
+For help with reporting issues look at the [how to report an issue](/community/reporting_issues).
 
 The easiest way to get started working with the code base is to pick up a really easy
 JIRA and work on that. This will help you get familiar with the code base, build system,
@@ -85,7 +85,7 @@ It’s better for everyone if we maintain discipline about the scope of each pat
 In general, if you find a bug while working on a specific feature, file a JIRA for the bug, check if you can assign it to yourself and fix it independently of the feature.
 This helps us to differentiate between bug fixes and features and allows us to build stable maintenance releases.
 
-Make sure you have observed the recommendations in the [coding guidelines](coding_guidelines).
+Make sure you have observed the recommendations in the [coding guidelines](/community/coding_guidelines).
 Before you commit your changes and create a pull request based on your changes you should run the code checks. 
 These same checks are run as part of the pull request workflow.
 The pull request workflow performs the following checks:
@@ -133,7 +133,7 @@ We follow the version numbering as described in the [version numbering](https://
 The master branch *must* use a pseudo version.
 See the [Go module dependencies](/docs/next/developer_guide/dependencies) for updating the pseudo version.
 The release branches *must* use branch version.
-See the [release procedure](release_procedure#tag-and-update-release-for-version) on when and how to update the tags and references during the release creation. 
+See the [release procedure](/community/release_procedure#tag-and-update-release-for-version) on when and how to update the tags and references during the release creation. 
 
 ## Documentation updates
 Documentation is published and maintained as part of the website.
diff --git a/src/pages/community/reporting_issues.md b/src/pages/community/reporting_issues.md
index 4c43a2f27..73e5728eb 100644
--- a/src/pages/community/reporting_issues.md
+++ b/src/pages/community/reporting_issues.md
@@ -34,7 +34,7 @@ Please do not disclose the issue to any public forum before working with the sec
 If you have an issue with YuniKorn operation, please follow these guidelines:
 
 If you are having an issue with setup, configuration, or some other form of behavior not matching your expectation, join the user mailing list and ask your questions in that forum.
-See the [Get Involved](get_involved#communication-channels) page for information on mailing lists.
+See the [Get Involved](/community/get_involved#communication-channels) page for information on mailing lists.
 You can also ask the YuniKorn slack channel for help, details on how to join can be found on the same page.
 If you have a bug that needs a fix in the code or in the documentation, please follow the procedure in [Filing a JIRA](#filing-a-jira-for-yunikorn-issues) below.