fix redirected links

Author: skshetry

.github/CONTRIBUTING.md

@@ -1,2 +1,2 @@
 **Please see our contributing guide at
-[dvc.org](https://doc.dvc.org/user-guide/contributing/docs).**
+[dvc.org](https://doc.dvc.org/contributing/docs).**

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,9 +1,9 @@
 > You may disregard these recommendations if you used the **Edit on GitHub** button from dvc.org to improve a doc in place.
 
-❗ Please read the guidelines in the [Contributing to the Documentation](https://doc.dvc.org/user-guide/contributing/docs) list if you make any substantial changes to the documentation or JS engine.
+❗ Please read the guidelines in the [Contributing to the Documentation](https://doc.dvc.org/contributing/docs) list if you make any substantial changes to the documentation or JS engine.
 
 🐛 Please make sure to mention `Fix #issue` (if applicable) in the description of the PR. This causes GitHub to close it automatically when the PR is merged.
 
-Please choose to [allow us](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork) to edit your branch when creating the PR.
+Please choose to [allow us](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork) to edit your branch when creating the PR.
 
 Thank you for the contribution - we'll try to review it as soon as possible. 🙏

README.md

@@ -7,9 +7,8 @@
 
 # Contributing Docs
 
-Please see our
-[Contributing guide](https://doc.dvc.org/user-guide/contributing/docs) for more
-details. Thanks to all our contributors!
+Please see our [Contributing guide](https://doc.dvc.org/contributing/docs) for
+more details. Thanks to all our contributors!
 
 [![Contributors](https://contrib.rocks/image?repo=iterative/dvc.org)](https://github.com/iterative/dvc.org/graphs/contributors)
 

content/docs/api-reference/dvcfilesystem.md

@@ -1,9 +1,9 @@
 # DVCFileSystem
 
 DVCFileSystem provides a pythonic file interface (
-[fsspec-compatible](https://filesystem-spec.readthedocs.io/)) for a DVC repo. It
-is a read-only filesystem, hence it does not support any write operations, like
-`put_file`, `cp`, `rm`, `mv`, `mkdir` etc.
+[fsspec-compatible](https://filesystem-spec.readthedocs.io/en/latest/)) for a
+DVC repo. It is a read-only filesystem, hence it does not support any write
+operations, like `put_file`, `cp`, `rm`, `mv`, `mkdir` etc.
 
 ```py
 class DVCFileSystem(AbstractFileSystem):
@@ -172,14 +172,15 @@ subdirectory.
 
 ## fsspec API Reference
 
-As DVCFileSystem is based on [fsspec](https://filesystem-spec.readthedocs.io/),
-it is compatible with most of the APIs that it offers. When DVC is installed in
-the same Python environment as any other fsspec-compatible library (such as
-[Hugging Face Datasets][hf-datasets]), DVCFileSystem will be used automatically
-when a `dvc://` filesystem URL is provided to fsspec function calls. For more
-details check out the fsspec's [API Reference][fsspec-api].
+As DVCFileSystem is based on
+[fsspec](https://filesystem-spec.readthedocs.io/en/latest/), it is compatible
+with most of the APIs that it offers. When DVC is installed in the same Python
+environment as any other fsspec-compatible library (such as [Hugging Face
+Datasets][hf-datasets]), DVCFileSystem will be used automatically when a
+`dvc://` filesystem URL is provided to fsspec function calls. For more details
+check out the fsspec's [API Reference][fsspec-api].
 
-[fsspec]: https://filesystem-spec.readthedocs.io/
+[fsspec]: https://filesystem-spec.readthedocs.io/en/latest/
 [fsspec-api]:
   https://filesystem-spec.readthedocs.io/en/latest/api.html#fsspec.spec.AbstractFileSystem
 [hf-datasets]: /user-guide/integrations/huggingface#hugging-face-datasets

content/docs/api-reference/open.md

@@ -149,7 +149,7 @@ usage), and is typically faster than loading the whole data into memory.
 
 This is just a matter of using the right `repo` argument, for example an SSH URL
 (requires that the
-[credentials are configured](https://help.github.com/en/github/authenticating-to-github/connecting-to-github-with-ssh)
+[credentials are configured](https://docs.github.com/en/authentication/connecting-to-github-with-ssh)
 locally):
 
 ```py

content/docs/command-reference/dag.md

@@ -67,7 +67,7 @@ $ dvc exp show ...
   [fenced code block](https://www.markdownguide.org/extended-syntax/#fenced-code-blocks).
 
   This can be used to combine `dvc dag` with
-  [`cml send-comment`](https://cml.dev/doc/ref/send-comment)
+  [`cml comment create`](https://cml.dev/doc/ref/comment#create)
 
 - `--mermaid` - show DAG in [Mermaid](https://mermaid-js.github.io) format. It
   can be passed to third party visualization utilities.
@@ -166,13 +166,13 @@ When the `--md` flag is passed, the mermaid output will be wrapped inside a
 Markdown
 [fenced code block](https://www.markdownguide.org/extended-syntax/#fenced-code-blocks).
 Note that this output is automatically rendered as a diagram
-[in GitHub](https://github.blog/2022-02-14-include-diagrams-markdown-files-mermaid/)
+[in GitHub](https://github.blog/developer-skills/github/include-diagrams-markdown-files-mermaid/)
 and [in GitLab](https://docs.gitlab.com/ee/user/markdown.html#mermaid).
 
 <admon type="tip">
 
 You can combine `dvc dag --md` with the
-[`cml send-comment`](https://cml.dev/doc/ref/send-comment) of CML:
+[`cml comment create`](https://cml.dev/doc/ref/comment#create) of CML:
 
 ```cli
 dvc dag --md >> dag.md

content/docs/command-reference/diff.md

@@ -146,7 +146,7 @@ files summary: 1 added, 0 deleted, 0 modified
 
 [2-track-data]:
   https://github.com/iterative/example-get-started/releases/tag/2-track-data
-[data versioning]: /start/data-management/data-versioning
+[data versioning]: /start
 
 ## Example: Comparing tags or branches
 

content/docs/command-reference/exp/branch.md

@@ -39,7 +39,7 @@ version.
   https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging
 [persistent]:
   /user-guide/experiment-management/sharing-experiments#persist-experiment
-[stored and shared]: /start/data-management/data-versioning#storing-and-sharing
+[stored and shared]: /start#storing-and-sharing
 
 ## Options
 

content/docs/command-reference/freeze.md

@@ -1,7 +1,7 @@
 # freeze
 
-Freeze [stages](/command-reference/run) until `dvc unfreeze` is used on them.
-Frozen stages are never executed by `dvc repro`.
+Freeze [stages](/command-reference/stage/add) until `dvc unfreeze` is used on
+them. Frozen stages are never executed by `dvc repro`.
 
 ## Synopsis
 
@@ -14,8 +14,8 @@ positional arguments:
 
 ## Description
 
-`dvc freeze` causes the [stages](/command-reference/run) indicated as `targets`
-to be considered _not changed_ by `dvc status` and `dvc repro`. Stage
+`dvc freeze` causes the [stages](/command-reference/stage/add) indicated as
+`targets` to be considered _not changed_ by `dvc status` and `dvc repro`. Stage
 reproduction will not regenerate <abbr>outputs</abbr> of frozen stages, even if
 their <abbr>dependencies</abbr> have changed, and even if `--force` is used.
 

content/docs/command-reference/get.md

@@ -123,9 +123,9 @@ the source Git repo. Instead, it's exported in the `dvc.yaml` file as an
 `dvc pull` the file from the `dvc remote default` of the source DVC project
 (found in [its config file]).
 
-[root directory]: https://github.com/iterative/example-get-started/tree/master/
+[root directory]: https://github.com/iterative/example-get-started/tree/main/
 [its config file]:
-  https://github.com/iterative/example-get-started/blob/master/.dvc/config
+  https://github.com/iterative/example-get-started/blob/main/.dvc/config
 
 <admon type="info">
 
@@ -230,8 +230,7 @@ Untracked files:
 ```
 
 [get started example repo]: https://github.com/iterative/example-get-started
-[switching between versions]:
-  /start/data-management/data-versioning#switching-between-versions
+[switching between versions]: /start#switching-between-versions
 
 ## Example: Set AWS profile for default remote