d91591f guides/user: Fixup scope default change formatting — radicle.xyz

rad:z371PVmDHdjJucejRoRYJcDEvD5pp

Radicle website including documentation and guides

guides/user: Fixup scope default change formatting

Adrian Duke committed 1 month ago

commit d91591f4789efdae3037bcfa9cd7c8d05b193d22
parent 9b1e2c4

1 file changed +2 -4

modified _guides/user.md

@@ -461,8 +461,6 @@ nodes. In the early stages of the Radicle network, all public repositories are

 automatically seeded by `iris.radicle.xyz` and `rosa.radicle.xyz` which
 are *public seed nodes* run by the core team.
 <!-- TODO: Talk about seeding policies and following -->
 <aside class="span-2"> <strong>Seed nodes</strong> are always-on machines that
 significantly enhance the network’s capacity to provide continuous access to
 repositories. They can vary in their seeding policies, from public seed nodes

@@ -718,7 +716,7 @@ some way, for example by pushing a branch or commenting on an issue, simply run

 > 👾
 >
 > The set of peers that are followed in the context of a seeded repository is
 > called the scope.
 > called the *scope*.
 >
 > By default, when cloning or seeding a repository, your node will subscribe to
 > content from the **repository delegates plus any node explicitly followed via**

@@ -1437,7 +1435,7 @@ synchronized to your device.

 You can change this behavior by specifying a different scope when cloning or
 initializing a repository, with the `--scope` option. For example, `--scope
 followed` will only synchronize changes by peers you explicitly follow with the
 `rad follow` command and the delegates. The default is `--scope followed`.
 `rad follow` command and the delegates. This is default behaviour.
 But if a peer becomes a regular collaborator, it would be useful to add them as
 a Git remote to track their changes and `checkout` their branches, even if