[Documentation] PushCase README standardization edits #593
Conversation
This file contains 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
|
ACK Nice catch, I agree and note:
So no linkability was lost, just indirected in a clear-to-find way. This is much more appropriate for a foss project. |
|
Agree with the changes suggested and support moving enclosures eventually to a dedicated repo in the future. |
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
The other enclosures included in our repo are just matter-of-fact presentations of their design.
My edits strip out the designer's personal references to external social media links, donation addr, and store url.
A later TODO: fully standardize ALL enclosure READMEs in the repo via a formal template (see #592).
This pull request is categorized as a: