Docs: fix RST formatting/linkage issues resulting in build warnings #40
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Towards closing #35, though it won't resolve it fully since I have decided not to tackle any docstring-related warnings from the Sphinx build, since with #39 these will resolve themselves, so it doesn't seem worthwhile to fix-up docstrings until that conversion. Therefore this PR addresses and fixes all errors and warnings from the Sphinx build that don't concern the docstrings.
Additionally, add some built source images that were missing from the repo, so they will show (notably one on the index page).
No review requested.