Fixed minor issues in manpage.

Fixed minor issues in manpage, e.g. capitalization, line breaks,
indentation and missing Doxygen markup.

Author: jriesmeier

dcmdata/docs/dcm2json.man

@@ -134,8 +134,8 @@ bulk data URI options:
          write bulk data files to d (default: '.')
 
   +bs  --bulk-subdir
-          create subdirectory for each SOP instance
-          (default: no subdirectory)
+         create subdirectory for each SOP instance
+         (default: no subdirectory)
 \endverbatim
 
 \subsection dcm2json_output_options output options
@@ -321,22 +321,19 @@ the following (see DICOM Part 18 Section F for details):
 
 By default, binary data, i.e. DICOM element values with Value Representations
 (VR) of OB, OD, OF, OL, OV, OW, and UN values are written as "InlineBinary"
-(base64 encoding) to the JSON output.
-Option \e --bulk-enabled causes binary data as well as
-DS, FD, FL, IS, SV and UV to be replaced by "BulkDataURI" values if the
-element value is larger than the cut-off threshold (default: 1 kByte).
-The cut-off threshold can be specified with the \e --bulk-size option.
-The element values themselves are written as files to the directory
-given by the \e --bulk-dir option (default: current directory).
-The filename is based on a SHA-256 checksum of the element value.
-By default, file URIs are generated that point to the bulk directory.
-For production use, a URI prefix for a WADO-RS service over which the
-element values can be retrieved should be specified using the
-\e --bulk-uri-prefix option. This can be implemented by configuring
-a web server that has read access to \b dcm2json's bulk directory.
-Finally, the option \e --bulk-subdir will cause a separate
-subdirectory to be created (and used in the bulk data URI) for each
-distinct SOP instance.
+(base64 encoding) to the JSON output.  Option \e --bulk-enabled causes binary
+data as well as DS, FD, FL, IS, SV and UV to be replaced by "BulkDataURI"
+values if the element value is larger than the cut-off threshold (default: 1
+kByte).  The cut-off threshold can be specified with the \e --bulk-size option.
+The element values themselves are written as files to the directory given by
+the \e --bulk-dir option (default: current directory).  The filename is based
+on a SHA-256 checksum of the element value.  By default, file URIs are
+generated that point to the bulk directory.  For production use, a URI prefix
+for a WADO-RS service over which the element values can be retrieved should be
+specified using the \e --bulk-uri-prefix option.  This can be implemented by
+configuring a web server that has read access to \b dcm2json's bulk directory.
+Finally, the option \e --bulk-subdir will cause a separate subdirectory to be
+created (and used in the bulk data URI) for each distinct SOP instance.
 
 Note that the JSON syntax for the representation of encapsulated pixel data
 in "InlineBinary" form is unspecified in DICOM, as is the JSON representation
@@ -379,8 +376,8 @@ parsers cannot process larger numbers.
 \subsection dcm2json_character_encoding Character Encoding
 
 As required by the DICOM JSON encoding, \b dcm2json always creates output in
-Unicode UTF-8 encoding and converts DICOM datasets accordingly.  If this is not
-possible, for example because DCMTK has been compiled without character set
+Unicode UTF-8 encoding and converts DICOM data sets accordingly.  If this is
+not possible, for example because DCMTK has been compiled without character set
 conversion support, an error is returned.
 
 \section dcm2json_logging LOGGING

dcmdata/docs/json2dcm.man

@@ -335,11 +335,11 @@ case is not defined in the DICOM standard yet.
 
 \subsection json2dcm_trailing_commas Trailing Commas
 
-Trailing commas are not permitted in JSON, but \b json2dcm will still
-accept such JSON datasets without warning or error message because they
-are handled gracefully by the underlying JSON parser. Users should, therefore,
-not assume that a JSON dataset is valid just because json2dcm accepts it.
-This tool is not designed as a validator for JSON or the DICOM JSON model.
+Trailing commas are not permitted in JSON, but \b json2dcm will still accept
+such JSON data sets without warning or error message because they are handled
+gracefully by the underlying JSON parser.  Users should, therefore, not assume
+that a JSON data set is valid just because \b json2dcm accepts it.  This tool
+is not designed as a validator for JSON or the DICOM JSON Model.
 
 \section json2dcm_logging LOGGING