docs: update concepts sidebar (#523)

Author: adohe

docs/kusion/2-getting-started/2-deliver-quickstart.md

@@ -102,7 +102,7 @@ network = { oci = "oci://ghcr.io/kusionstack/network", tag = "0.2.0" }
 ```
 
 :::info
-More details about the application model and module dependency declaration can be found in [Kusion Module guide for app dev](../3-concepts/3-kusion-module/3-app-dev-guide.md). 
+More details about the application model and module dependency declaration can be found in [Kusion Module guide for app dev](../3-concepts/3-module/3-app-dev-guide.md). 
 :::
 
 :::tip

docs/kusion/3-concepts/1-project/_category_.json

@@ -1,3 +1,3 @@
 {
-    "label": "Project"
+    "label": "Projects"
 }

docs/kusion/3-concepts/2-stack/_category_.json

@@ -1,3 +1,3 @@
 {
-    "label": "Stack"
+    "label": "Stacks"
 }

docs/kusion/3-concepts/3-kusion-module/_category_.json

@@ -0,0 +1,3 @@
+{
+    "label": "Modules"
+}

docs/kusion/3-concepts/3-kusion-module/1-overview.md renamed to docs/kusion/3-concepts/3-module/1-overview.md

@@ -1,6 +1,6 @@
 ---
 id: workspace
-sidebar_label: Workspace
+sidebar_label: Workspaces
 ---
 
 # Workspace
@@ -71,7 +71,7 @@ The values of the same fields in `patcher` will override the `default`, and one
 
 In the `patcher`, the applied Projects are assigned by the field `ProjectSelector`, which is an array of the Project names. The `ProjectSelector` is provided rather than something may like `StackSelector`, which specifies the applied Stacks. Here are the reasons. Explaining from the perspective of using Workspace, the mapping of Workspace and Stack is specified by the Kusion operation commands' users. While explaining from the perspective of the relationship among Project, Stack and Workspace, Workspace is designed for the reuse of platform-level configuration among multiple Projects. When a Project "encounters" a Workspace, it becomes a "Stack instance", which can be applied to a series of real resources. If using something like `StackSelector`, the reuse would not get realized, and Workspace would also lose its relevance. For more information of the relationship, please refer to [Project](project/overview) and [Stack](stack/overview). 
 
-Different Module and KAM has different name, fields, and corresponding format and restrictions. When writing the configuration, check the corresponding Module's or KAM's description, and make sure all the requisite Modules and KAMs have correctly configured. Please refer to [Kuiosn Module](kusion-module/overview) and find more information. The example above gives a sample of the Module `mysql`.
+Different Module and KAM has different name, fields, and corresponding format and restrictions. When writing the configuration, check the corresponding Module's or KAM's description, and make sure all the requisite Modules and KAMs have correctly configured. Please refer to [Kuiosn Module](module/overview) and find more information. The example above gives a sample of the Module `mysql`.
 
 ## Managing Workspace
 

docs/kusion/3-concepts/3-kusion-module/2-develop-guide.md renamed to docs/kusion/3-concepts/3-module/2-develop-guide.md

@@ -1,6 +1,6 @@
 ---
 id: backend
-sidebar_label: Backend
+sidebar_label: Backends
 ---
 
 # Backend