# Guide copyedits ## Protocol Guide ### Item 1 > Every Radicle user, irrespective of their role or activity, operates a node by installing a [Radicle Node](#) on their device. - The Radicle Node hyperlink needs to be fixed - "operates a node by installing a Radicle Node" is an odd statement, as the word "node" is redundant. - option 1: simplify it with "installs a Radicle Node on their device." - option 2: In a later section, this is said "To run a node and connect to the network, users install a Radicle client." which also seems inconsistent with saying users install a Radicle node ? Should above sentence in question also say client instead of node? ### Item 2 > Users configure nodes with a seeding policy which specifies the list of repositories they are interested in seeding, in addition to retention rules. This means that nodes aren’t just seeding random repositories, users have an active role in deciding which repositories should be stored on their device. - Replace with something more like this (more accurate as far as describing the configuration process): - Whenever a user clones, initializes, or opts to seed a repository, their node's *seeding policy* is modified to reflect their choices. This policy establishes the repositories they are interested in seeding and sets the rules for data retention, allowing users to have direct control over which repositories are kept on their device, rather than indiscriminately seeding any repository. ### Item 3 > The reference implementation can be found in the Radicle heartwood repository - Radicle Heartwood ? capitalize heartwood? ### Item 4 > The Radicle networking layer is designed as a gossip protocol, where messages are sent relayed between peers to build routing tables that aid in repository discovery and replication. - 'sent relayed' seems like a typo ### Item 5 > gossip messages may be temporarily stored and replayed to nodes joining the network for the first time, or after a long period of being offline. - did you mean to use the word "replayed" or should that be relayed? ### Item 6 > the *working copy*, and a remote “stored” copy that is interacted with via git push and git fetch, using Radicle’s git-remote-helper. - use italics for the word *stored copy* and remove the quotes around "stored" ### Item 7 - have the word "stored copy" in the diagram visuals ![image](https://hackmd.io/_uploads/rJnPE2Z2T.png) ### Item 8 > In Radicle, COBs allow for social artifacts to be stored directly inside repository, and replicated between peers. - "directly inside a repository" ### Item 9 > When the histories of two peers are synchronized, the commit graphs are simplied unioned with each other in a non-destructive, idempotent way. - "are simply unioned" - define "idempotent" in side bar ??