docs: fix a couple of minor docs typos

Signed-off-by: Tim Rogowski <7815824+trogowski@users.noreply.github.com>

Author: trogowski

docs/reference/lang/codelab/collaborative.md

@@ -83,7 +83,7 @@ In order to complete the collaborative configuration development, we first need
 │           └── main.k
 ├── kcl.mod
 └── pkg
-    └── sever.k
+    └── server.k
 ```
 
 The directory of the project mainly contains three parts:
@@ -280,7 +280,7 @@ server:
     env: dev
 ```
 
-Using the same method, we can build the production configuration, write the code in the `dev/main.k` file, and add a label to it.
+Using the same method, we can build the production configuration, write the code in the `prod/main.k` file, and add a label to it.
 
 ```python
 import pkg

docs/reference/lang/codelab/schema.md

@@ -526,7 +526,7 @@ nginx = Nginx {
 ```python
 nginx = NginxProd {
     labels.run = "my-nginx"
-    labels.env = "pre-prod"
+    labels.env = "prod"
 }
 ```
 
@@ -575,10 +575,10 @@ Now, we can complete the declaration of the server configuration through the Dep
 
 However, usually, the actual situation is more complicated, and the deployment may have a variety of optional variable accessories.
 
-For example, we want to support a persistent volume claim based on an existing schema, as a reusable Kubernetes schema. In this case, we can just wrapper it with a `mixin` and a `protocol` as follows:
+For example, we want to support a persistent volume claim based on an existing schema, as a reusable Kubernetes schema. In this case, we can just wrap it with a `mixin` and a `protocol` as follows:
 
 ```python
-import k8spkg.api.core.v1
+import k8s.api.core.v1
 
 protocol PVCProtocol:
     pvc?: {str:}
@@ -604,6 +604,12 @@ mixin PersistentVolumeClaimMixin for PVCProtocol:
         }
 ```
 
+> Note: for the `k8s.api.core.v1` import to work, we need to initialize a module and add the `k8s` module as a dependency:
+> ```bash
+> kcl mod init
+> kcl mod add k8s
+> ```
+
 With this PersistentVolumeClaimMixin, we define a PVC schema with a clear `user interface`, and use Kubernetes PVC as an implementation. Then, we can define a server schema with Deployment schema, and PVC mixin schema.
 
 ```

docs/reference/lang/codelab/simple.md

@@ -450,7 +450,7 @@ _priorityCpuMap = {
     "3" = 1024
 }
 # Using a dict to simplify logic and the default value is 2048
-_cpu = _priorityCpuMap[_priority] or 2048
+_cpu = _priorityCpuMap[str(_priority)] or 2048
 _name = "nginx"
 # exported variables
 cpu = _cpu