Fix argument format for calculatepackageid command (#4993)

This patch updates the argument format for `calculatepackageid` command,
enclosing `packageFile` in square brankets to indicate that the specific
file name should be put.

Signed-off-by: Tatsuya Sato <tatsuya.sato.so@hitachi.com>

docs/source/commands/peercommand.md

@@ -5,7 +5,7 @@
  The `peer` command has five different subcommands, each of which allows
  administrators to perform a specific set of tasks related to a peer.  For
  example, you can use the `peer channel` subcommand to join a peer to a channel,
- or the `peer  chaincode` command to deploy a smart contract chaincode to a
+ or the `peer chaincode` command to deploy a smart contract chaincode to a
  peer.
 
 ## Syntax

docs/source/commands/peerlifecycle.md

@@ -200,7 +200,7 @@ Global Flags:
 Calculate the package ID for a packaged chaincode.
 
 Usage:
-  peer lifecycle chaincode calculatepackageid packageFile [flags]
+  peer lifecycle chaincode calculatepackageid [packageFile] [flags]
 
 Flags:
       --connectionProfile string       The fully qualified path to the connection profile that provides the necessary connection information for the network. Note: currently only supported for providing peer connection information

internal/peer/lifecycle/chaincode/calculatepackageid.go

@@ -52,7 +52,7 @@ func (i *CalculatePackageIDInput) Validate() error {
 // the package ID for a packaged chaincode
 func CalculatePackageIDCmd(p *PackageIDCalculator) *cobra.Command {
 	calculatePackageIDCmd := &cobra.Command{
-		Use:       "calculatepackageid packageFile",
+		Use:       "calculatepackageid [packageFile]",
 		Short:     "Calculate the package ID for a chaincode.",
 		Long:      "Calculate the package ID for a packaged chaincode.",
 		ValidArgs: []string{"1"},