Skip to content

policy: Do a bunch of docs fixes #565

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jul 14, 2023

Conversation

tcharding
Copy link
Member

Three patches, the first two simple. The third is a bunch of mixed rustdoc fixes. Just sing out if this is too painful to review. I did this while attempting to understand the module better.

The comment on why we use semantic and abstract interchangeable is
better placed in the `semantic` module docs.
Currently the `translate_pk` functions on `semantic::Policy` and
`concrete::Policy` have exactly the same docs in the `# Examples`
section, down to the usage of "abstract" in both.

Direct docs readers from one function to the other to see the example.
Put some love and care into the docs in the `policy` module:

- Use standard tense on functions
- Use full sentences
- Fix grammar/spelling/typos
- Tidy up rustdoc examples
- Use standard section headers (eg, `# Returns`)
- Fix links
- Use backticks

I doubt this is perfect because fixing (and reviewing) docs is a bit
boring but I'm confident it is an improvement :)

There was a couple of functions that I could not re-write the docs for
at the time I did this work but I've misplaced them for now.
Copy link
Member

@apoelstra apoelstra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK 1bd3070

@apoelstra apoelstra merged commit 33676d1 into rust-bitcoin:master Jul 14, 2023
@tcharding tcharding deleted the 07-03-policy-cleanup branch July 25, 2023 06:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants