Slight corrections of appearance

Slightly modified the discrepancy from the actual results of the deployment-in-namespace command execution.

Author: smecsia

01-path-basics/103-kubernetes-concepts/readme.adoc

@@ -1447,21 +1447,21 @@ Alternatively, a namespace can be created using `kubectl` as well.
 . Create a Deployment:
 
 	$ kubectl -n dev2 apply -f deployment.yaml
-	deployment "nginx-deployment-ns" created
+	deployment "nginx-deployment" created
 
 . Get Deployments in the newly created Namespace:
 
 	$ kubectl get deployments -n dev2
 	NAME               DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
-	nginx-deployment-ns   3         3         3            3           1m
+	nginx-deployment   3         3         3            3           1m
 
 . Get Deployments in all Namespaces:
 
 	$ kubectl get deployments --all-namespaces
 	NAMESPACE     NAME                  DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
 	default       nginx-deployment      3         3         3            3           1h
 	dev           nginx-deployment-ns   3         3         3            3           1h
-	dev2          nginx-deployment-ns   3         3         3            3           1m
+	dev2          nginx-deployment      3         3         3            3           1m
 	kube-system   dns-controller        1         1         1            1           5h
 	kube-system   kube-dns              2         2         2            2           5h
 	kube-system   kube-dns-autoscaler   1         1         1            1           5h
@@ -1634,8 +1634,8 @@ Note, how CPU and memory resources have incremented values.
 
 https://github.com/kubernetes/kubernetes/issues/55433[kubernetes#55433] provide more details on how an explicit CPU resource is not needed to create a Pod with ResourceQuota.
 
-$ kubectl delete quota/quota
-$ kubectl delete quota/quota2
+	$ kubectl delete quota/quota
+	$ kubectl delete quota/quota2
 
 You are now ready to continue on with the workshop!