Adjust the article location to below the test directory.

Author: heisen-li

src/doc/src/SUMMARY.md

@@ -9,12 +9,12 @@
 * [Cargo Guide](guide/index.md)
     * [Why Cargo Exists](guide/why-cargo-exists.md)
     * [Creating a New Package](guide/creating-a-new-project.md)
-    * [Creating a Workspace](guide/creating-a-new-workspace.md)
     * [Working on an Existing Package](guide/working-on-an-existing-project.md)
     * [Dependencies](guide/dependencies.md)
     * [Package Layout](guide/project-layout.md)
     * [Cargo.toml vs Cargo.lock](guide/cargo-toml-vs-cargo-lock.md)
     * [Tests](guide/tests.md)
+    * [Creating a Workspace](guide/creating-a-new-workspace.md)
     * [Continuous Integration](guide/continuous-integration.md)
     * [Cargo Home](guide/cargo-home.md)
     * [Build Cache](guide/build-cache.md)

src/doc/src/guide/creating-a-new-workspace.md

@@ -22,6 +22,7 @@ Currently `Cargo` does not provide automatic creation of workspaces using the co
 If using a virtual workspace, then the version of [resolver] needs to be specified in the table (if not, the default version of resolver for a workspace is `1`, even if the default resolver version for workspace members is `2`), for example:
 
 ```toml
+# [new_workspace]/Cargo.toml
 [workspace]
 resolver = "2"
 ```
@@ -69,5 +70,6 @@ $ tree .
 
 Up to this point, we have achieved creating a workspace that contains multiple `crate` members through a step-by-step process.
 
+
 [def-workspace]:  ../appendix/glossary.md#workspace  '"workspace" (glossary entry)'
 [resolver]: ../reference/resolver.md