Unnamed repository; edit this file 'description' to name the repository.
| -rw-r--r-- | docs/book/src/contributing/README.md | 2 | ||||
| -rw-r--r-- | docs/book/src/troubleshooting.md | 3 |
2 files changed, 2 insertions, 3 deletions
diff --git a/docs/book/src/contributing/README.md b/docs/book/src/contributing/README.md index 5f4a74eba2..beb94cdfc4 100644 --- a/docs/book/src/contributing/README.md +++ b/docs/book/src/contributing/README.md @@ -13,7 +13,7 @@ To learn more about how rust-analyzer works, see [Architecture](architecture.md) It also explains the high-level layout of the source code. Do skim through that document. -We also publish rustdoc docs to pages: https://rust-lang.github.io/rust-analyzer/ide/. +We also publish rustdoc docs to <https://rust-lang.github.io/rust-analyzer/ide/>. Note though, that the internal documentation is very incomplete. Various organizational and process issues are discussed in this document. diff --git a/docs/book/src/troubleshooting.md b/docs/book/src/troubleshooting.md index 4092b9de99..1b2841421a 100644 --- a/docs/book/src/troubleshooting.md +++ b/docs/book/src/troubleshooting.md @@ -46,5 +46,4 @@ It is especially useful when the `repo` doesn’t use external crates or the standard library. If you want to go as far as to modify the source code to debug the -problem, be sure to take a look at the [dev -docs](https://github.com/rust-lang/rust-analyzer/tree/master/docs/dev)! +problem, be sure to take a look at the [contribution guide](contributing/index.html)! |