Fix broken links

Signed-off-by: Pavithra Eswaramoorthy <[email protected]>

Author: pavithraes

docs/community/issues.md

@@ -47,13 +47,13 @@ If an issue is affecting you, start at the top of this list and complete as many
 
 1. Check the [issue tracker][nebari-issues], if there is an open issue for this same problem, add a reaction or more details to the issue
    to indicate that it’s affecting you (tip: make sure to also check the open [pull requests][nebari-prs] for ongoing work).
-2. You should also check the [troubleshooting guide](../troubleshooting.mdx) in these docs to see if your problem is already listed there.
+2. You should also check the [troubleshooting guide][troubleshooting] in these docs to see if your problem is already listed there.
 3. If there is an open issue, and you can add more detail, write a comment describing how the problem is affecting you,
    OR if you can, write up a work-around or improvement for the issue.
 4. If there is not an issue, write the most complete description of what’s happening including reproduction steps.
 5. [Optional] - Offer to help fix the issue (and it is totally expected that you ask for help; open-source maintainers want to help contributors).
 <!-- 6. TODO link to the PR section of the docs -->
-6. If you decide to help to fix the issue, deliver a well-crafted, tested PR.
+1. If you decide to help to fix the issue, deliver a well-crafted, tested PR.
 
 ## Working on issues to improve them
 
@@ -66,7 +66,11 @@ The following actions are typically useful:
 - Linking to related issues or discussions while briefly describing how they are related, for instance “See also #xyz for a similar attempt at this” or “See also #xyz where the same thing happened in another cloud provider" provides context and helps the discussion.
 - Summarizing long discussions on issues to help new and existing contributors quickly understand the background, current status, and course of action for the issue.
 
-<!-- links -->
+<!-- Internal links -->
+
+[troubleshooting]: /docs/troubleshooting.mdx
+
+<!-- External Links -->
 
 [nebari-issues]: https://github.com/nebari-dev/nebari/issues
 [nebari-labels]: https://github.com/nebari-dev/nebari/labels

docs/community/maintainers/triage-guidelines.md

@@ -129,5 +129,5 @@ Support requests should be directed to the following channels:
 
 [code-contributions]: community/code-contributions.mdx
 [github-conventions]: community/maintainers/github-conventions.md
-[troubleshooting]: ../../troubleshooting.mdx
-[saved-replies]: ./saved-replies.md
+[troubleshooting]: docs/troubleshooting.mdx
+[saved-replies]: community/maintainers/saved-replies.md

docs/community/nebari-tests.md

@@ -11,7 +11,7 @@ This page has some tips for testing your contributions to make sure it works as
 
 ### Test CLI manually
 
-If you have an [editable installation of Nebari](code-contributions#install-nebari-in-editable-mode), you can test your changes by running the [Nebari CLI commands](../get-started/quickstart) from within your development environment.
+If you have an [editable installation of Nebari](code-contributions#install-nebari-in-editable-mode), you can test your changes by running the [Nebari CLI commands][quickstart] from within your development environment.
 For example, you can run `nebari init` and make sure it builds the `nebari-config.yaml` file without errors.
 
 ### Test CLI with `pytest`
@@ -80,7 +80,7 @@ It can help you review and resolve day-to-day issues in the deployed clusters qu
 
 You can install `k9s` on macOS, Windows, and Linux with [these instructions project's README](https://github.com/derailed/k9s).
 
-For more details on using `k9s`, check out the [documentation on debugging Nebari](../how-tos/debug-nebari#debugging-the-kubernetes-cluster-using-k9s).
+For more details on using `k9s`, check out the [documentation on debugging Nebari][debugging-nebari].
 
 ### Cloud testing
 
@@ -233,3 +233,8 @@ To get around this, set the `NEBARI_K8S_VERSION` environment variable with:
 ```bash
 export NEBARI_K8S_VERSION=1.20
 ```
+
+<!-- Internal links -->
+
+[quickstart]: docs/get-started/quickstart
+[debugging-nebari]: docs/how-tos/debug-nebari#debugging-the-kubernetes-cluster-using-k9s

docs/community/style-guide.md

@@ -30,7 +30,7 @@ Follow your best judgment, and feel free to add to this document following our c
 - **Avoid abbreviations** like "e.g.", "i.e.", and "etc.". Use full words like "for example", "that is", and "and so on" respectively.
 - Use **serial commas**, also known as Oxford comma. For example: "Nebari brand uses purple, yellow, and green."
 - Leave **only one blank space between sentences**.
-- **Break up long lines in code snippets** with "`\`" for better readability. For example, see the code block in [Automatic DNS provision](../how-tos/domain-registry#automatic-dns-provision).
+- **Break up long lines in code snippets** with "`\`" for better readability. For example, see the code block in [Automatic DNS provision][automatic-dns-provision].
 - Try and **use [semantic line breaks](https://sembr.org/)** to help with documentation and contribution reviews.
 - **Prefer American English** over British or other English variant to keep spelling consistency.
 
@@ -99,3 +99,7 @@ For example: "To start JupyterLab, you run `jupyter lab`."
 - The [Microsoft Writing Style Guide](https://learn.microsoft.com/en-gb/style-guide/welcome/) is also a very thorough style guide. The included A-Z word list is a handy reference if you're unsure about a specific term.
 - [Digital Ocean's tutorial style guide](https://www.digitalocean.com/community/tutorials/digitalocean-s-technical-writing-guidelines).
 - [Write the Docs collection of resources for accessible writing](https://www.writethedocs.org/guide/writing/accessibility/).
+
+<!-- Internal links -->
+
+[automatic-dns-provision]: docs/how-tos/domain-registry#automatic-dns-provision

docs/docs/welcome.mdx

@@ -150,9 +150,9 @@ Learn to perform specific tasks in Nebari, with step-by-step instructions.
 
 Nebari is a community-led open source project, learn how you can get involved!
 
-> [Facing issues with Nebari? Get support on GitHub discussions or the issue tracker →](./community#getting-support)
+> [Facing issues with Nebari? Get support on GitHub discussions or the issue tracker →](docs/community#getting-support)
 
-> [Learn how you can contribute to Nebari, beyond code and pull-requests →](./community#how-to-contribute)
+> [Learn how you can contribute to Nebari, beyond code and pull-requests →](docs/community#how-to-contribute)
 
 [↳ Read all community resources][community]
 
@@ -180,13 +180,13 @@ Understand technical details of Nebari's architecture and how it works.
 <!-- Internal links -->
 
 [nebari-home]: https://nebari.dev/
-[get-started]: ./category/get-started
-[tutorials]: ./tutorials/
-[how-tos]: ./how-tos/
-[community]: ./community/
-[references]: ./references
-[release-notes]: ./references/RELEASE
-[using-dask]: ./tutorials/using_dask
-[using-vscode]: ./how-tos/using-vscode
-[configure-keycloak]: ./how-tos/configuring-keycloak
-[create-dashboards]: ./tutorials/create-dashboard
+[get-started]: docs/get-started/
+[tutorials]: docs/tutorials/
+[how-tos]: docs/how-tos/
+[community]: community/
+[references]: docs/references
+[release-notes]: docs/references/RELEASE
+[using-dask]: docs/tutorials/using_dask
+[using-vscode]: docs/how-tos/using-vscode
+[configure-keycloak]: docs/how-tos/configuring-keycloak
+[create-dashboards]: docs/tutorials/create-dashboard