diff --git a/xCAT-client/pods/man1/updatenode.1.pod b/xCAT-client/pods/man1/updatenode.1.pod
index 52c2dceaa..4ce71f579 100644
--- a/xCAT-client/pods/man1/updatenode.1.pod
+++ b/xCAT-client/pods/man1/updatenode.1.pod
@@ -334,13 +334,24 @@ Update the ca and credentials to the service nodes.
 
 =item B<-P|--scripts>
 
-Specifies that postscripts should be run on the nodes.
+Specifies that postscripts should be run on the nodes. 
 updatenode -P syncfiles is not supported.  The syncfiles postscript can only
-be run during install.  You should use updatenode <noderange> -F instead.
+be run during install.  You should use updatenode <noderange> -F instead. 
 
 =item B<-S|--sw>
 
-Specifies that node software should be updated.
+Specifies that node software should be updated. It is equivalent to running the 
+folloiwng command:
+
+ updatenode noderange -P ospkgs,otherpkgs
+
+It will update all the rpms specified in the .pkglist file and .otherpkgs.pkglist 
+file. ospkgs postscript will normally remove all the existing rpm 
+repositories before adding server:/install/<os>/<arch/ as the new repository. 
+To preserve the existing repositories, you can run the following command instead:
+
+updatenode noderange -P "ospkgs --keeprepo,otherpkgs"
+
 
 =item B<-s|--sn>
 
@@ -425,7 +436,8 @@ the following command is equivalent:
 
 B<updatenode clstrn01 "script1 p1 p2,script2">
 
-p1 p2 are parameters for script1.
+p1 p2 are parameters for script1. 
+ 
 
 =item 6
 
diff --git a/xCAT-client/pods/man1/xdcp.1.pod b/xCAT-client/pods/man1/xdcp.1.pod
index 4547d9fcc..1fe5bdefa 100644
--- a/xCAT-client/pods/man1/xdcp.1.pod
+++ b/xCAT-client/pods/man1/xdcp.1.pod
@@ -31,6 +31,7 @@ remote node or device appended to  the  copied  source_file  name.  The
 If using hierarchy, then xdcp runs on the service node that is servicing the compute node. The file will first be copied to the path defined in the site table, SNsyncfiledir attribute, or the default path /var/xcat/syncfiles on the service node, if the attribute is not defined. The -P flag will not automatically copy
 the files from the compute node to the Management node, hierarchically.  There
 is a two step process, see -P flag.  
+If the Management Node is target node, it must be defined in the xCAT database with nodetype=mn.When the B<xdcp> command runs the Management Node as the target, it does not use remote commands but uses the local OS copy (cp) command. 
 
 B<REMOTE> B<USER>:
 
diff --git a/xCAT-client/pods/man1/xdsh.1.pod b/xCAT-client/pods/man1/xdsh.1.pod
index 44fc7cd6d..c60f18ed8 100644
--- a/xCAT-client/pods/man1/xdsh.1.pod
+++ b/xCAT-client/pods/man1/xdsh.1.pod
@@ -1,6 +1,6 @@
 =head1 B<NAME>
 
-B<xdsh> - Concurrently runs commands on multiple nodes, or an install image.
+B<xdsh> - Concurrently runs commands on multiple nodes (Management Node, Service Nodes, compute nodes), or an install image.
 
 =head1 B<SYNOPSIS>
 
@@ -21,16 +21,17 @@ B<xdsh> [B<-h> | B<-V> | B<-q>]
 
 =head1 B<DESCRIPTION>
 
-The B<xdsh> command runs commands in parallel on remote nodes.  The B<xdsh> command issues  a
+The B<xdsh> command runs commands in parallel on remote nodes and/or the Management Node.   The B<xdsh> command issues  a
 remote  shell command for each target specified, and returns the output
 from all targets,
 formatted so that command results  from  all  nodes  can  be  managed.
+If the command is to be executed  on the Management Node, it does not use a remote shell command, but uses the local OS copy or shell command. The Management Node must be defined in the xCAT database and have a nodetype of mn. 
 The B<xdsh> command is an xCAT Distributed Shell Utility.
 
 
 B<COMMAND> B<SPECIFICATION>:
 
-The commands to execute on the remote  targets  are  specified  by  the
+The commands to execute on the  targets  are  specified  by  the
 I<command_list>  B<xdsh>  parameter, or executing a local script using the B<-e>
 flag.