Fix some config.toml documentation

Author: webmaster128

src/pages/sylvia/basics/generate-contract.mdx

@@ -91,8 +91,8 @@ way you want.
 - `src/multitest/` - module in which we define our tests. It's a good practice to separate the tests
   between files semantically.
 - `src/bin/schema.rs` - builds into a binary which generates the contract schema.
-- `.cargo/config` - exposes some aliases to make working with the project simpler.
+- `.cargo/config.toml` - exposes some aliases to make working with the project simpler.
   - `cargo wasm` - run `cargo build` with additional options to compile a proper _wasm_ binary.
-  - `cargo wasm-debug` - same as `cargo wasm`, but without `--release` profile to provide more
-    debugging symbols.
-  - `cargo schema` - builds and runs the `src/schema.rs` for simpler schema generation.
+  - `cargo wasm-debug` - same as `cargo wasm`, but without `--release` profile to speed up build
+    times a lot and provide debugging symbols.
+  - `cargo schema` - builds and runs the `src/bin/schema.rs` for simpler schema generation.

src/pages/tutorial/cw-contract/building-contract.mdx

@@ -37,9 +37,8 @@ wasm = "build --target wasm32-unknown-unknown --release"
 wasm-debug = "build --target wasm32-unknown-unknown"
 ```
 
-Now, building your Wasm binary is as easy as executing `cargo wasm`. We also added the additional
-`wasm-debug` command for rare cases when we want to build the wasm binary, including debug
-information.
+Now, building your Wasm binary is as easy as executing `cargo wasm`. We also added the `wasm-debug`
+command for faster test builds and rare cases when we want to include debug information in the Wasm.
 
 ## Checking contract validity
 

src/pages/tutorial/cw-contract/good-practices.mdx

@@ -280,13 +280,13 @@ I encourage you to go to the generated file to see what the schema looks like.
 
 The problem is that, unfortunately, creating this binary makes our project fail to compile on the
 Wasm target - which is, in the end, the most important one. Fortunately, we don't need to build the
-schema binary for the Wasm target - let's align the `.cargo/config` file:
+schema binary for the Wasm target - let's align the `.cargo/config.toml` file:
 
 ```toml
 [alias]
 wasm = "build --target wasm32-unknown-unknown --release --lib"
 wasm-debug = "build --target wasm32-unknown-unknown --lib"
-schema = "run schema"
+schema = "run --bin schema"
 ```
 
 The `--lib` flag added to `wasm` cargo aliases tells the toolchain to build only the library