"cryptic-net network" -> "cryptic network" throughout docs

docs/admin/adding-a-host-to-the-network.md

@@ -4,7 +4,7 @@ This document guides an admin through adding a single host to the network. Keep
 in mind that the steps described here must be done for _each_ host the user
 wishes to add.
 
-There are two ways for a user to add a host to the cryptic-net network.
+There are two ways for a user to add a host to the cryptic network.
 
 - If the user is savy enough to obtain their own `cryptic-net` binary, they can
   do so. The admin can then generate a `bootstrap.yml` file for their host,

docs/admin/creating-a-new-network.md

@@ -1,9 +1,9 @@
 # Creating a New Network
 
-This guide is for those who wish to start a new cryptic-net network of their
+This guide is for those who wish to start a new cryptic network of their
 own.
 
-By starting a new cryptic-net network, you are becoming the administrator of a
+By starting a new cryptic network, you are becoming the administrator of a
 network. Be aware that being a network administrator is not necessarily easy,
 and the users of your network will frequently need your help in order to have a
 good experience. It can be helpful to have others with which you are
@@ -83,8 +83,8 @@ be chosen with care.
 ## Step 3: Prepare to Encrypt `admin.yml`
 
 The `admin.yml` file (which will be created in the next step) is the most
-sensitive part of a cryptic-net network. If it falls into the wrong hands it can
-be used to completely compromise your network, impersonate hosts on the network,
+sensitive part of a cryptic network. If it falls into the wrong hands it can be
+used to completely compromise your network, impersonate hosts on the network,
 and will likely lead to someone stealing or deleting all of your data.
 
 Therefore it is important that the file remains encrypted when it is not being

docs/dev/design-principles.md

@@ -16,6 +16,6 @@ cryptic-net project.
   dispersed.
 
 * It is expected that a single host might be a part of multiple, independent
-  cryptic-net networks. These should not conflict with each other, nor share
+  cryptic networks. These should not conflict with each other, nor share
   resources.
 

entrypoint/src/cmd/entrypoint/admin.go

@@ -49,7 +49,7 @@ func readAdmin(path string) (admin.Admin, error) {
 
 var subCmdAdminCreateNetwork = subCmd{
 	name:  "create-network",
-	descr: "Creates a new cryptic-net network, outputting the resulting admin.yml to stdout",
+	descr: "Creates a new cryptic network, outputting the resulting admin.yml to stdout",
 	do: func(subCmdCtx subCmdCtx) error {
 
 		flags := subCmdCtx.flagSet(false)