Repository navigation
docs: improve wording in deploying Python applications guide - #2162
Closed
Bilalabdulkadir wants to merge 2 commits into
Closed
Bilalabdulkadir wants to merge 2 commits into
Bilalabdulkadir wants to merge 2 commits into
Conversation
Previous wording made it sound like all the keys were required.
Clarify JSON response for Simple API has "up to" 5 keys
Contributor
|
The branch contents don’t match the PR title, the target branch is wrong, there is no issue linked. Closing for now, please re-create when correct. |
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
4 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.
Summary
This pull request improves the documentation by clarifying wording and improving readability.
Changes
📚 Documentation preview 📚: https://python-packaging-user-guide--2162.org.readthedocs.build/en/2162/