Use HTTPS URIs in README, fix query params in RST for Directory API docs #538
Conversation
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
|
Thanks for your contribution and attention to detail! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This is a small update (IMHO) to gpodder.net documentation.
I noticed that links to Read the Docs used insecure HTTP URIs, whereas HTTPS is available. The change to the README updates these links to HTTPS.
In the Directory API documentation I noticed broken descriptions of query parameters in two endpoints, while other endpoints had correct descriptions.
Based on the working descriptions, I changed
::queryto:queryin the ReStructuredText for the Directory API.