diff --git a/doc/manual/nix-store.xml b/doc/manual/nix-store.xml
index a168be024..da3eae2ec 100644
--- a/doc/manual/nix-store.xml
+++ b/doc/manual/nix-store.xml
@@ -779,4 +779,178 @@ archive is read from standard input.
+
+
+Operation
+
+
+ Synopsis
+
+ nix-store
+
+ paths
+
+
+
+Description
+
+The operation writes a serialisation
+of the specified store paths to standard output in a format that can
+be imported into another Nix store with nix-store --import. This
+is like nix-store
+--dump, except that the NAR archive produced by that command
+doesn’t contain the necessary meta-information to allow it to be
+imported into another Nix store (namely, the set of references of the
+path).
+
+This command does not produce a closure of
+the specified paths, so if a store path references other store paths
+that are missing in the target Nix store, the import will fail. To
+copy a whole closure, do something like
+
+
+$ nix-store --export $(nix-store -qR paths) > out
+
+
+
+For an example of how and
+ can be used, see the source of the nix-copy-closure
+command.
+
+
+
+
+
+
+
+
+
+Operation
+
+
+ Synopsis
+
+ nix-store
+
+
+
+
+Description
+
+The operation reads a serialisation of
+a set of store paths produced by nix-store --import from
+standard input and adds those store paths to the Nix store. Paths
+that already exist in the Nix store are ignored. If a path refers to
+another path that doesn’t exist in the Nix store, the import
+fails.
+
+
+
+
+
+
+
+
+
+Operation
+
+
+ Synopsis
+
+ nix-store
+
+
+
+
+Description
+
+The operation reduces Nix store disk
+space usage by finding identical files in the store and hard-linking
+them to each other. It typically reduces the size of the store by
+something like 25-35%. Only regular files and symlinks are
+hard-linked in this manner. Files are considered identical when they
+have the same NAR archive serialisation: that is, regular files must
+have the same contents and permission (executable or non-executable),
+and symlinks must have the same contents.
+
+After completion, or when the command is interrupted, a report
+on the achieved savings is printed on standard error.
+
+Use or to get some
+progress indication.
+
+
+
+Example
+
+
+$ nix-store --optimise
+hashing files in `/nix/store/qhqx7l2f1kmwihc9bnxs7rc159hsxnf3-gcc-4.1.1'
+...
+541838819 bytes (516.74 MiB) freed by hard-linking 54143 files;
+there are 114486 files with equal contents out of 215894 files in total
+
+
+
+
+
+
+
+
+
+
+Operation
+
+
+ Synopsis
+
+ nix-store
+
+
+
+
+ paths
+
+
+
+Description
+
+The operation prints the build log
+of the specified store paths on standard output. The build log is
+whatever the builder of a derivation wrote to standard output and
+standard error. If a store path is not a derivation, the deriver of
+the store path is used.
+
+Build logs are kept in
+/nix/var/log/nix/drvs. However, there is no
+guarantee that a build log is available for any particular store
+path. For instance, if the path was downloaded as a pre-built binary
+through a substitute, then the log is unavailable.
+
+
+
+Example
+
+
+$ nix-store -l $(which ktorrent)
+building /nix/store/dhc73pvzpnzxhdgpimsd9sw39di66ph1-ktorrent-2.2.1
+unpacking sources
+unpacking source archive /nix/store/p8n1jpqs27mgkjw07pb5269717nzf5f8-ktorrent-2.2.1.tar.gz
+ktorrent-2.2.1/
+ktorrent-2.2.1/NEWS
+...
+
+
+
+
+
+
+
+
+
+
+