Update plugin docs to cleanup formatting issues #353
Merged
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
6 tasks
dedemorton
force-pushed
the
update_plugin_docs_5.2
branch
from
8159f66 to
1406bfd
Compare
dedemorton
force-pushed
the
update_plugin_docs_5.2
branch
from
1406bfd to
0b78121
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
I ran the docgen tool one last time and then did some manual cleanup because there were still quite a few nits in the plugin docs.
The changes are not as extensive as they seem. I did a global search/replace and forgot that my editor was set to trim trailing spaces. :-/ Doh.
When I generate the plugin docs for 5.3, hopefully most of these issues will be resolved, but if not...I'll know what to look out for.