diff --git a/xCAT-buildkit/pods/man1/buildkit.1.pod b/xCAT-buildkit/pods/man1/buildkit.1.pod
index 0ef435936..61e43294c 100644
--- a/xCAT-buildkit/pods/man1/buildkit.1.pod
+++ b/xCAT-buildkit/pods/man1/buildkit.1.pod
@@ -21,7 +21,7 @@ B<buildkit> [B<-V> | B<--verbose>] B<cleantar>
 
 B<buildkit> [B<-V> | B<--verbose>] B<cleanall>
 
-B<buildkit> [B<-V> | B<--verbose>] B<addpkgs> I<kit_tarfile> {B<-p> | B<--pkgdir>} I<package_directory>
+B<buildkit> [B<-V> | B<--verbose>] B<addpkgs> I<kit_tarfile> {B<-p> | B<--pkgdir>} {B<-k> | B<--kitversion> I<version>} {B<-r> | B<--kitrelease> I<release>} I<package_directory>
 
 B<command> [B<-?> | B<-h> | B<--help> | B<-v> | B<--version>]
 
@@ -74,10 +74,14 @@ List the repos defined in your buildkit configuration file:
 
 =item 8.
 
-For each reponame listed, build the repository.  Note that if you need to build repositories for OS distributions or versions that do not match the current system, you may need to copy your kit template directory to an appropriate server to build that repository, and then copy the results back to your main build server.
+For each reponame listed, build the repository.  Note that if you need to build repositories for OS distributions, versions, or architectures that do not match the current system, you may need to copy your kit template directory to an appropriate server to build that repository, and then copy the results back to your main build server.
 
      buildkit buildrepo repo_name 
 
+or, you can build all of the repos at one time if there are no OS or architecture dependencies for kitcomponent package builds or kitpackage builds:
+
+     buildkit buildrepo all
+
 =item 9.
 
 Build the kit tar file:
@@ -123,19 +127,19 @@ Reads the buildkit.conf file from the current directory, and deletes all the pac
 
 =item  B<buildtar> 
 
-Reads the buildkit.conf file from the current directory, validates that all kit repositories have been built, and builds the Kit tar file <cwd>/build/I<kitname>.tar.bz2.
+Reads the buildkit.conf file from the current directory, validates that all kit repositories have been built, and builds the Kit tar file <cwd>/I<kitname>.tar.bz2.
 
 =item  B<cleantar> 
 
-Reads the buildkit.conf file from the current directory, deletes the Kit tar <cwd>/build/I<kitname>.tar.bz2, and deletes all files in the build work directory <cwd>/build/I<kitname>.
+Reads the buildkit.conf file from the current directory, deletes the Kit tar <cwd>/I<kitname>.tar.bz2, and deletes all files in the build work directory <cwd>/build/I<kitname>.
 
 =item  B<cleanall>
 
 Equivalent to running B<buildkit cleanrepo all> and B<buildkit cleantar>.
 
-=item  B<addpkgs> I<kit_tarfile> {B<-p> | B<--pkgdir>} I<package_directory>
+=item  B<addpkgs> I<kit_tarfile> {B<-p> | B<--pkgdir>} {B<-k> | B<--kitversion> I<version>} {B<-r> | B<--kitrelease> I<release>} I<package_directory>
 
-Add product package rpms to a previously built kit tar file.  This is used for product kits that are built and shipped separately from the product packages.
+Add product package rpms to a previously built kit tar file.  This is used for incomplete product kits that are built and shipped separately from the product packages, and are identified with a I<kit_tarfile> name of I<kitname>.B<NEED_PRODUCT_PKGS.tar.bz2>. Optionally, change the kit release and version values when building the new kit tarfile.  If kitcomponent version and/or release values are defaulted to the kit values, those will also be changed and new kitcomponent rpms will be built.  If kit or kitcomponent scripts, plugins, or other files specify name, release, or version substitution strings, these will all be replaced with the new values when built into the new complete kit tarfile I<cwd>/I<new_kitname>.B<tar.bz2>.
 
 =back
 
@@ -169,7 +173,7 @@ To create the sample kit shipped with the xCAT-buildkit rpm on a RHELS 6.3 serve
    vi buildkit.conf
    buildkit chkconfig
    buildkit listrepo
-   buildkit buildrepo rhels6.3
+   buildkit buildrepo all 
    buildkit buildtar
 
 =item 2.
@@ -199,7 +203,7 @@ To clean up all kit build files, including a previously built kit tar file, run
 
 <cwd>/build/I<kitname>/kit.conf
 
-<cwd>/build/I<kitname>.tar.bz2
+<cwd>/I<kitname>.tar.bz2
 
 
 =head1 SEE ALSO