Improve links and references in dims module notebook#8069
Open
AdishreeB wants to merge 1 commit intopymc-devs:mainfrom
Open
Improve links and references in dims module notebook#8069AdishreeB wants to merge 1 commit intopymc-devs:mainfrom
AdishreeB wants to merge 1 commit intopymc-devs:mainfrom
Conversation
|
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
This file contains hidden or 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.
Description
This PR improves the dims module notebook by adding proper links to the relevant
dims API documentation (distributions, transforms, and math) and by using a Sphinx
{doc}instead ofhard-coded URLs with references for better robustness and
version-awareness.
Where specific distributions (e.g.
ZeroSumNormal,Categorical) are mentioned,the notebook now links to their corresponding API documentation entries, making
it easier for readers to explore related functionality.
No behavioural or API changes are introduced; this PR only improves documentation
clarity and navigation.
Related Issue
Checklist
Type of change