Adjust chapter content to be guidance rather than practice.

Author: heisen-li

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

@@ -3,24 +3,83 @@
 A [workspace][def-workspace] is a collection of one or more packages, 
 called workspace members, that are managed together.
 
-In this chapter we implement the creation of a workspace `new_workspace` from scratch, 
-in which two members `foo-bin` and `bar-lib` are included.
+In this chapter, we will create a workspace `new_workspace` containing 
+binary member `foo` and library member `bar`.
 
 As mentioned in [`[workspace]` section][workspace-section], the workspace must 
-have at least one member, either the [root package] or a [virtual manifest]. 
-Here we recommend setting the root of the workspace to be a virtual manifest. 
-The reason is as follows:
+have at least one member, either the [root package] or a [virtual manifest].
 
-- The crate namespace at the Cargo level is flat. The tree layout creates 
-another hierarchy and increases the possibility of inconsistencies. 
-- With a flat structure, adding or splitting crates is very easy. 
-- Even larger flattened lists are easier to see at a glance and easier to 
-maintain than smaller tree structures.
+Next we create a workspace containing [root package].
+For convenience, you can first create a package using the command `cargo new new_workspace`.
+Then add the `[workspace]` section to the `Cargo.toml` file in the root directory 
+to make it a manifest of the workspace:
+
+```toml
+# [new_workspace]/Cargo.toml
+[workspace]
+
+[package]
+name = "new_workspace"
+version = "0.1.0"
+edition = "2021"
+
+# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
+
+[dependencies]
+```
+
+Then, continue adding members `foo` and `bar` to the workspace:
+
+```console
+$ cd new_workspace
+$ cargo new foo
+$ cargo new bar --lib
+```
+
+Cargo will automatically add members to `Cargo.toml`。
+At this point, the workspace will contain three members: `foo` and `bar` and 
+the default member `new_workspace`.
+
+```toml
+# [new_workspace]/Cargo.toml
+[workspace]
+members = [ "bar", "foo" ]
+
+[package]
+name = "new_workspace"
+version = "0.1.0"
+edition = "2021"
+
+# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
+
+[dependencies]
+```
+
+The package at this point contains the following files:
+
+```console
+$ cd new_workspace
+$ tree .
+.
+├── bar
+│   ├── Cargo.toml
+│   └── src
+│       └── lib.rs
+├── Cargo.toml
+├── foo
+│   ├── Cargo.toml
+│   └── src
+│       └── main.rs
+└── src
+    └── main.rs
+
+5 directories, 6 files
+```
 
 Let's move on and create a virtual workspace.
 
-Currently `Cargo` does not provide automatic creation of workspaces using the command line. 
-You need to create the `Cargo.toml` file under the folder `new_workspace`:
+In the another `new_workspace` empty directory, create a new `Cargo.toml` file and 
+add the `[workspace]` section:
 
 ```toml
 # [new_workspace]/Cargo.toml
@@ -37,26 +96,15 @@ even if the default resolver version for workspace members is `2`), for example:
 resolver = "2"
 ```
 
-You can then proceed to create workspace members. As mentioned above, 
-if you have a lot of workspace members, we recommend designing the workspace 
-with a flat structure. So add all the workspace members in the directory `new_workspace/crates`.
+Likewise, you can then use the `cargo new <package>` command to create 
+binary member `foo` and library member `bar`.
 
-There are several ways to add members to the workspace, we recommend using the 
-command `cargo new/init`. For example, add the members `foo-bin` and `bar-lib` 
-to the workspace:
-
-```console
-$ cargo new crates/foo-bin
-$ cargo new crates/bar-lib --lib
-```
-
-Cargo will automatically add members to `Cargo.toml`:
 
 ```toml
 # [new_workspace]/Cargo.toml
 [workspace]
 resolver = "2"
-members = [ "crates/bar-lib","crates/foo-bin"]
+members = [ "bar","foo"]
 
 ```
 
@@ -66,26 +114,25 @@ The package at this point contains the following files:
 $ cd new_workspace
 $ tree .
 .
+├── bar
+│   ├── Cargo.toml
+│   └── src
+│       └── lib.rs
 ├── Cargo.toml
-└── crates
-    ├── bar-lib
-    │   ├── Cargo.toml
-    │   └── src
-    │       └── lib.rs
-    └── foo-bin
-        ├── Cargo.toml
-        └── src
-            └── main.rs
-
-5 directories, 5 files
+└── foo
+    ├── Cargo.toml
+    └── src
+        └── main.rs
+
+4 directories, 5 files
 ```
 
 Up to this point, we have a workspace with two members.
 Whenever you run `cargo build` under the workspace root directory, Cargo builds 
 all member at once.
 Instead of building the entire workspace, you could use the `--package`/`-p` flag 
 to select certain packages.
-For example, `cargo build -p foo-bin` will build only `foo-bin` package.
+For example, `cargo build -p foo` will build only `foo` package.
 
 [workspace-section]: ../reference/workspaces.md#the-workspace-section
 [root package]:      ../reference/workspaces.md#root-package