v0.2.48..v0.2.49 changeset changeset apply.asciidoc

diff --git a/docs/commands/changeset-apply.asciidoc b/docs/commands/changeset-apply.asciidoc
index 8073d54..d99b298 100644
--- a/docs/commands/changeset-apply.asciidoc
+++ b/docs/commands/changeset-apply.asciidoc
@@ -3,31 +3,21 @@
 
 === Description
 
-The +changeset-apply+ command writes a OSM changeset XML file(s) (.osc or .xml) or a SQL changeset
-file (.osc.sql) to an OSM API database.
-
-Optional conflict parameters may be passed for SQL files, so that if the target database contains
-any changesets created after the time represented by a timestamp that intersect with a specified
-AOI, the command will return an error.
-
-* +changeset.os*+     - one or more input OSM XML changeset (.osc file) or OSM XML file (.osm) with
-                        negative IDs when writing the changeset through the OSM API OR an input SQL
-                        changeset (.osc.sql) when writing the changeset directly to an OSM API
-                        database
-* +targetUrl+         - If writing the changeset through the OSM API, the OSM API endpoint the
-                        changeset will be written to; if writing the changeset directly to an OSM
-                        API database, the URL of the database being written to
-* +conflictAoi+       - bounding box string of the form: minx,miny,maxx,maxy used to prevent writing
-                        conflicted
-                        data (see description); valid only when writing the changeset directly to an
-                        OSM API database
-* +conflictTimestamp+ - timestamp of the form: "yyyy-MM-dd hh:mm:ss.zzz" used to prevent writing
-                        conflicted
-                        data (see description); valid only when writing the changeset directly to an
-                        OSM API database
-* +--stats+           - output statistics (element, node, way, relation, failure, create, modify,
-                        and delete counts)
-* +--progress+        - display progress as a percent complete while the upload is working
+The +changeset-apply+ command writes a OSM changeset XML file(s) (.osc or .xml) or a SQL changeset file (.osc.sql) to an OSM API database.
+
+Optional conflict parameters may be passed for SQL files, so that if the target database contains any changesets created after the time 
+represented by a timestamp that intersect with a specified AOI, the command will return an error.
+
+* +changeset.os*+     - One or more input OSM XML changeset (.osc file) or OSM XML file (.osm) with negative IDs when writing the changeset 
+                        through the OSM API OR an input SQL changeset (.osc.sql) when writing the changeset directly to an OSM API database.
+* +targetUrl+         - If writing the changeset through the OSM API, the OSM API endpoint the changeset will be written to; if writing the 
+                        changeset directly to an OSM API database, the URL of the database being written to
+* +conflictAoi+       - Bounding box string of the form: minx,miny,maxx,maxy used to prevent writing conflicted data (see description); valid 
+                        only when writing the changeset directly to an OSM API database
+* +conflictTimestamp+ - Timestamp of the form: "yyyy-MM-dd hh:mm:ss.zzz" used to prevent writing conflicted data (see description); valid only 
+                        when writing the changeset directly to an OSM API database
+* +--stats+           - Output statistics (element, node, way, relation, failure, create, modify, and delete counts)
+* +--progress+        - Display progress as a percent complete while the upload is working
 
 === Usage