1 files changed, 47 insertions, 48 deletions
diff --git a/iredis/data/commands/xadd.md b/iredis/data/commands/xadd.md
index 8a80556..d651a68 100644
--- a/iredis/data/commands/xadd.md
+++ b/iredis/data/commands/xadd.md
@@ -1,67 +1,71 @@
-Appends the specified stream entry to the stream at the specified key. If the
-key does not exist, as a side effect of running this command the key is created
-with a stream value. The creation of stream's key can be disabled with the
-`NOMKSTREAM` option.
+Appends the specified stream entry to the stream at the specified key.
+If the key does not exist, as a side effect of running this command the
+key is created with a stream value. The creation of stream's key can be
+disabled with the `NOMKSTREAM` option.
 
-An entry is composed of a set of field-value pairs, it is basically a small
-dictionary. The field-value pairs are stored in the same order they are given by
-the user, and commands to read the stream such as `XRANGE` or `XREAD` are
-guaranteed to return the fields and values exactly in the same order they were
-added by `XADD`.
+An entry is composed of a list of field-value pairs.
+The field-value pairs are stored in the same order they are given by the user.
+Commands that read the stream, such as `XRANGE` or `XREAD`, are guaranteed to return the fields and values exactly in the same order they were added by `XADD`.
 
-`XADD` is the _only Redis command_ that can add data to a stream, but there are
-other commands, such as `XDEL` and `XTRIM`, that are able to remove data from a
-stream.
+`XADD` is the *only Redis command* that can add data to a stream, but 
+there are other commands, such as `XDEL` and `XTRIM`, that are able to
+remove data from a stream.
 
 ## Specifying a Stream ID as an argument
 
 A stream entry ID identifies a given entry inside a stream.
 
 The `XADD` command will auto-generate a unique ID for you if the ID argument
-specified is the `*` character (asterisk ASCII character). However, while useful
-only in very rare cases, it is possible to specify a well-formed ID, so that the
-new entry will be added exactly with the specified ID.
+specified is the `*` character (asterisk ASCII character). However, while
+useful only in very rare cases, it is possible to specify a well-formed ID, so
+that the new entry will be added exactly with the specified ID.
 
 IDs are specified by two numbers separated by a `-` character:
 
     1526919030474-55
 
-Both quantities are 64-bit numbers. When an ID is auto-generated, the first part
-is the Unix time in milliseconds of the Redis instance generating the ID. The
-second part is just a sequence number and is used in order to distinguish IDs
-generated in the same millisecond.
-
-IDs are guaranteed to be always incremental: If you compare the ID of the entry
-just inserted it will be greater than any other past ID, so entries are totally
-ordered inside a stream. In order to guarantee this property, if the current top
-ID in the stream has a time greater than the current local time of the instance,
-the top entry time will be used instead, and the sequence part of the ID
-incremented. This may happen when, for instance, the local clock jumps backward,
-or if after a failover the new master has a different absolute time.
-
-When a user specified an explicit ID to `XADD`, the minimum valid ID is `0-1`,
-and the user _must_ specify an ID which is greater than any other ID currently
-inside the stream, otherwise the command will fail and return an error. Usually
+Both quantities are 64-bit numbers. When an ID is auto-generated, the
+first part is the Unix time in milliseconds of the Redis instance generating
+the ID. The second part is just a sequence number and is used in order to
+distinguish IDs generated in the same millisecond.
+
+You can also specify an incomplete ID, that consists only of the milliseconds part, which is interpreted as a zero value for sequence part.
+To have only the sequence part automatically generated, specify the milliseconds part followed by the `-` separator and the `*` character:
+
+```
+> XADD mystream 1526919030474-55 message "Hello,"
+"1526919030474-55"
+> XADD mystream 1526919030474-* message " World!"
+"1526919030474-56"
+```
+
+IDs are guaranteed to be always incremental: If you compare the ID of the
+entry just inserted it will be greater than any other past ID, so entries
+are totally ordered inside a stream. In order to guarantee this property,
+if the current top ID in the stream has a time greater than the current
+local time of the instance, the top entry time will be used instead, and
+the sequence part of the ID incremented. This may happen when, for instance,
+the local clock jumps backward, or if after a failover the new master has
+a different absolute time.
+
+When a user specified an explicit ID to `XADD`, the minimum valid ID is
+`0-1`, and the user *must* specify an ID which is greater than any other
+ID currently inside the stream, otherwise the command will fail and return an error. Usually
 resorting to specific IDs is useful only if you have another system generating
-unique IDs (for instance an SQL table) and you really want the Redis stream IDs
-to match the one of this other system.
+unique IDs (for instance an SQL table) and you really want the Redis stream
+IDs to match the one of this other system.
 
 ## Capped streams
 
-`XADD` incorporates the same semantics as the `XTRIM` command - refer to its
-documentation page for more information. This allows adding new entries and
-keeping the stream's size in check with a single call to `XADD`, effectively
-capping the stream with an arbitrary threshold. Although exact trimming is
-possible and is the default, due to the internal representation of streams it is
-more efficient to add an entry and trim stream with `XADD` using **almost
-exact** trimming (the `~` argument).
+`XADD` incorporates the same semantics as the `XTRIM` command - refer to its documentation page for more information.
+This allows adding new entries and keeping the stream's size in check with a single call to `XADD`, effectively capping the stream with an arbitrary threshold.
+Although exact trimming is possible and is the default, due to the internal representation of steams it is more efficient to add an entry and trim stream with `XADD` using **almost exact** trimming (the `~` argument).
 
 For example, calling `XADD` in the following form:
 
     XADD mystream MAXLEN ~ 1000 * ... entry fields here ...
-
-Will add a new entry but will also evict old entries so that the stream will
-contain only 1000 entries, or at most a few tens more.
+ 
+Will add a new entry but will also evict old entries so that the stream will contain only 1000 entries, or at most a few tens more.
 
 ## Additional information about streams
 
@@ -79,11 +83,6 @@ specified by the user during insertion.
 The command returns a @nil-reply when used with the `NOMKSTREAM` option and the
 key doesn't exist.
 
-@history
-
-- `>= 6.2`: Added the `NOMKSTREAM` option, `MINID` trimming strategy and the
-  `LIMIT` option.
-
 @examples
 
 ```cli