Tweak/fix metadata resolve docs.

Due to how markdown works there can't be blank lines in the embedded HTML.

Author: ehuss

src/doc/man/cargo-metadata.adoc

@@ -199,17 +199,14 @@ The output has the following format:
     "workspace_members": [
         "my-package 0.1.0 (path+file:///path/to/my-package)",
     ],
-    /* The resolved dependency graph, with the concrete versions and features
-       selected. The set depends on the enabled features.
-
-       All platform-specific dependencies are listed regardless of the current
-       target.
-
-       This is null if --no-deps is specified.
-       By default, this includes all dependencies for all target platforms.
-       The `--filter-platform` flag may be used to narrow to a specific
-       target triple.
-    */
+    // The resolved dependency graph, with the concrete versions and features
+    // selected. The set depends on the enabled features.
+    //
+    // This is null if --no-deps is specified.
+    //
+    // By default, this includes all dependencies for all target platforms.
+    // The `--filter-platform` flag may be used to narrow to a specific
+    // target triple.
     "resolve": {
         /* Array of nodes within the dependency graph.
            Each node is a package.

src/doc/man/generated/cargo-metadata.html

@@ -206,17 +206,14 @@ <h2 id="cargo_metadata_output_format">OUTPUT FORMAT</h2>
     "workspace_members": [
         "my-package 0.1.0 (path+file:///path/to/my-package)",
     ],
-    /* The resolved dependency graph, with the concrete versions and features
-       selected. The set depends on the enabled features.
-
-       All platform-specific dependencies are listed regardless of the current
-       target.
-
-       This is null if --no-deps is specified.
-       By default, this includes all dependencies for all target platforms.
-       The `--filter-platform` flag may be used to narrow to a specific
-       target triple.
-    */
+    // The resolved dependency graph, with the concrete versions and features
+    // selected. The set depends on the enabled features.
+    //
+    // This is null if --no-deps is specified.
+    //
+    // By default, this includes all dependencies for all target platforms.
+    // The `--filter-platform` flag may be used to narrow to a specific
+    // target triple.
     "resolve": {
         /* Array of nodes within the dependency graph.
            Each node is a package.
@@ -491,4 +488,4 @@ <h2 id="cargo_metadata_see_also">SEE ALSO</h2>
 <p><a href="index.html">cargo(1)</a></p>
 </div>
 </div>
-</div>
+</div>

src/etc/man/cargo-metadata.1

@@ -220,17 +220,14 @@ The output has the following format:
     "workspace_members": [
         "my\-package 0.1.0 (path+file:///path/to/my\-package)",
     ],
-    /* The resolved dependency graph, with the concrete versions and features
-       selected. The set depends on the enabled features.
-
-       All platform\-specific dependencies are listed regardless of the current
-       target.
-
-       This is null if \-\-no\-deps is specified.
-       By default, this includes all dependencies for all target platforms.
-       The `\-\-filter\-platform` flag may be used to narrow to a specific
-       target triple.
-    */
+    // The resolved dependency graph, with the concrete versions and features
+    // selected. The set depends on the enabled features.
+    //
+    // This is null if \-\-no\-deps is specified.
+    //
+    // By default, this includes all dependencies for all target platforms.
+    // The `\-\-filter\-platform` flag may be used to narrow to a specific
+    // target triple.
     "resolve": {
         /* Array of nodes within the dependency graph.
            Each node is a package.