Fix broken links in documentation

docs/releases/versioning.md

@@ -79,8 +79,6 @@ When work completes on an API version on the main development branch, a
 The name of that release is the API version.
 After a release is snapped, the API version on the main development branch
   is incremented and work begins on the next release.
-To learn more about our release process and workflow,
-  please see the [development model section].
 
 ## Application Binary Interface (ABI)
 
@@ -229,9 +227,8 @@ The deprecation period will depend on the impact of the change, but will usually
   last three to six months.
 
 
-[development model section]: ../contributing/development_model.md
-[releases section]: ./releases.md
-[changelog]: ./changelog.md
+[releases section]: ../releases.md
+[changelog]: changelog.md
 
 [semantic versioning]: https://semver.org
 [live at head]: https://www.youtube.com/watch?v=tISy7EJQPzI&t=1032s

docs/setup/requirements.md

@@ -98,10 +98,10 @@ To build and test libcu++ yourself, you will need the following in addition to
   - We recommend installing lit using Python's pip package manager.
 
 
-[Standard API section]: ./standard_api.md
-[Extended API section]: ./extended_api.md
-[synchronization library section]: ./standard_api/synchronization_library.html
-[changelog]: ./releases/changelog.md
+[Standard API section]: ../standard_api.md
+[Extended API section]: ../extended_api.md
+[synchronization library section]: ../extended_api/synchronization_primitives.md
+[changelog]: ../releases/changelog.md
 
 [NVIDIA HPC SDK]: https://developer.nvidia.com/hpc-sdk
 [CUDA Toolkit]: https://developer.nvidia.com/cuda-toolkit

docs/standard_api/utility_library/version.md

@@ -24,4 +24,4 @@ When using NVCC, the definition of C++ feature test macros is provided by the
   host Standard Library, not libcu++.
 
 
-[versioning section]: ./releases/versioning.md
+[versioning section]: ../../releases/versioning.md