diff options
| author | willcl-ark <will@256k1.dev> | 2024-05-02 21:30:59 +0100 |
|---|---|---|
| committer | willcl-ark <will@256k1.dev> | 2024-05-03 16:07:12 +0100 |
| commit | 4b9f49da2b120e81516ddc3dc577d7a2e58e02d3 (patch) | |
| tree | 4bd3d98b501fc583f90685c4da3bbbcdbad79a83 /doc/developer-notes.md | |
| parent | 9d1a286f20b8a602ffe72928bcd79be09fdbf9d0 (diff) | |
doc: fix broken relative md links
These relative links in our documentation are broken, fix them.
Diffstat (limited to 'doc/developer-notes.md')
| -rw-r--r-- | doc/developer-notes.md | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/doc/developer-notes.md b/doc/developer-notes.md index cc3f0518e5..3458a71467 100644 --- a/doc/developer-notes.md +++ b/doc/developer-notes.md @@ -334,7 +334,7 @@ Recommendations: - Avoid linking to external documentation; links can break. - Javadoc and all valid Doxygen comments are stripped from Doxygen source code - previews (`STRIP_CODE_COMMENTS = YES` in [Doxyfile.in](doc/Doxyfile.in)). If + previews (`STRIP_CODE_COMMENTS = YES` in [Doxyfile.in](/doc/Doxyfile.in)). If you want a comment to be preserved, it must instead use `//` or `/* */`. ### Generating Documentation @@ -1335,8 +1335,7 @@ Release notes should be written for any PR that: Release notes should be added to a PR-specific release note file at `/doc/release-notes-<PR number>.md` to avoid conflicts between multiple PRs. -All `release-notes*` files are merged into a single -[/doc/release-notes.md](/doc/release-notes.md) file prior to the release. +All `release-notes*` files are merged into a single `release-notes-<version>.md` file prior to the release. RPC interface guidelines -------------------------- |