[FAB-8763] Clarify CLI cc package doc for node cc

Similar to FAB-8731, this CR clarifies the usage of the path flag when
packaging a Node.js chaincode using the peer CLI.

Change-Id: I8139a15323b254998413967f2e0767a49332003a
Signed-off-by: Will Lahti <wtlahti@us.ibm.com>

docs/source/commands/peerchaincode.md

@@ -121,10 +121,10 @@ The `peer chaincode install` command has the following command-specific flags:
 
   * `-p, --path <string>`
 
-    Path to the chaincode that is being installed. For Golang (-l golang) chaincodes, this
-    is the path relative to the GOPATH. For Node.js (-l node) chaincodes, this is either the
-    absolute path or the relative path from where the install command is being
-    performed
+    Path to the chaincode that is being installed. For Golang (-l golang)
+    chaincodes, this is the path relative to the GOPATH. For Node.js (-l node)
+    chaincodes, this is either the absolute path or the relative path from where
+    the install command is being performed
 
   * `-v, --version <string>`
 
@@ -476,7 +476,10 @@ The `peer chaincode package` command has the following command-specific flags:
 
   * `-p, --path <string>`
 
-    Path, relative to the GOPATH, to the chaincode that is being installed
+    Path to the chaincode that is being packaged. For Golang (-l golang)
+    chaincodes, this is the path relative to the GOPATH. For Node.js (-l node)
+    chaincodes, this is either the absolute path or the relative path from where
+    the package command is being performed
 
   * `-s, --cc-package`