Addressed reviews

cmd/ipfs-cluster-ctl/main.go

@@ -272,8 +272,10 @@ which may not necessarily be the local ipfs daemon).
 Once the adding process is finished, the content is fully added to all
 allocations and pinned in them. This makes cluster add slower than a local
 ipfs add, but the result is a fully replicated CID on completion.
-If you prefer faster adding, add directly to the local IPFS and trigger a
-cluster "pin add".
+If you prefer faster adding, use the --local flag to add directly to the local
+IPFS node and pin in the destinations after that. Note that the local IPFS
+node may not be among the destinations, which will leave the unpinned content
+in it.
 
 Optional replication-min and replication-max factors can be provided: -1 means
 "pin everywhere" and 0 means use cluster's default setting (i.e., replication
@@ -340,7 +342,7 @@ content.
 				},
 				cli.BoolFlag{
 					Name:  "local",
-					Usage: "Puts blocks only in local IPFS peer and then pin as per PinOptions",
+					Usage: "Add to local peer but pin normally",
 				},
 				cli.StringFlag{
 					Name:  "name, n",

logging.go

@@ -37,7 +37,7 @@ var LoggingFacilities = map[string]string{
 	"apitypes":     "INFO",
 	"config":       "INFO",
 	"shardingdags": "INFO",
-	"localdags":    "INFO",
+	"singledags":   "INFO",
 	"adder":        "INFO",
 	"optracker":    "INFO",
 	"pstoremgr":    "INFO",