Skip to content
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

Copy edits #4

Draft
wants to merge 62 commits into
base: master
Choose a base branch
from
Draft

Copy edits #4

wants to merge 62 commits into from

Conversation

adamkdean
Copy link
Member

@adamkdean adamkdean commented Jan 25, 2022

Work in progress copy edits

Minor copy edits. Simplification, sentence structure.
Copy edits. As per TOV doc., I've shifted a lot of passive voice into active. This should make the copy feel lighter, more personable, and more direct. You'll find a fair few contractions where relevant, some formatting changes for legibility, and general simplification throughout.
Minor edits
Minor edits. Passive voice. Note on simplification: I've seen a fair bit of "prepositionalisation" — i.e. "the current and upcoming development focus [for the platform]". Moving forward, I'll shift this to standard possessive ("the platform's current and upcoming development focus") as a matter of course, as it noticeably improves readability.
I've moved away from "distributed computing paradigm" in favour of explaining what that is on Line 11.

Line 29: "the connectivity of devices in multifarious network settings" — I've leaned into "to connect easily" as opposed to "connectivity", as it's more active and less abstract. I'll probably think this way when I come across similar instances. I've also chosen to rework "multifarious network settings", and explain what's meant by that within the copy itself.

Line 49: "you can reduce north-south transport, effectively converting it to east-west transport between devices and end users within your own estate" — could someone clarify what's meant by this for me?
Minor edits
Minor edits
Note: I'm noticing lots of "present continuous" — e.g. "giving you one clean interface". Generally, I'll revise away from this as it can feel passive and intangible. 

Otherwise, minor edits.
A fair few structural simplifiers. 

I think we need an ELI5 on "reed-Solomon erasure coding"
I have displaced the mention of redundancy to line 31, along with an explanation of what that means. 

Question: Reed-Solomon erasure coding — does this differ from Reed-Solomon error correction?
We talk about usage in terms of "Individuals can do X"; I propose shifting to "You can do X". It's more inclusive, less hypothetical, and generally feels a bit friendlier.

"Purchases made in $EDGE are automatically bridged in to Edge Network and swapped for $XE." This got individual mention within the Service Purchase section, although it simply repeated what was said above. I've removed to avoid repetition.

Moderate switching of passive to active. A fair amount of simplification
Minor edits
Minor edits
@adamkdean adamkdean marked this pull request as draft January 25, 2022 10:54
Copy link
Contributor

@josephdenne josephdenne left a comment

Choose a reason for hiding this comment

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

I'm really happy with these updates. Any visual updates needed I'll do in situ in Gitbooks' interface post merge.

Typos and minor edits
Minor edits
Perform different functions --> Do different things
Other minor edits/typos
Formatting
Minor edits; simplicity
Minor edits; mainly passive --> active
Minor edits, typos.
Minor edits
Edits: simplicity
Edits, passive-->active, simplicity
Minor edit
Minor simplifications
Minor edits; typos, casing
Edits: voice, typos, simplification, casing
Very minor edits, typo
adamkdean pushed a commit that referenced this pull request Oct 11, 2022
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.

3 participants