diff --git a/.devcontainer/devcontainer.json b/.devcontainer/devcontainer.json
index 89c7382e..f0b69b50 100644
--- a/.devcontainer/devcontainer.json
+++ b/.devcontainer/devcontainer.json
@@ -44,26 +44,16 @@
 	"forwardPorts": [
 		30000,
 		30080,
-		30088,
-		31080,
-		31088,
 		32000,
-		32080,
-		32088,
-		32089
+		32080
 	],
 
 	// add labels
 	"portsAttributes": {
 		"30000": { "label": "Prometheus" },
-		"30080": { "label": "MyApp" },
-		"30088": { "label": "heartbeat" },
-		"31080": { "label": "IMDb" },
-		"31088": { "label": "dogs-cats" },
+		"30080": { "label": "Res-Edge-Ui" },
 		"32000": { "label": "Grafana" },
-		"32080": { "label": "Res-Edge" },
-		"32088": { "label": "tabs-spaces" },
-		"32089": { "label": "ArgoCD-dashboard" }
+		"32080": { "label": "Res-Edge-Api" }
 	},
 
 	"waitFor": "postCreateCommand",
diff --git a/README.md b/README.md
index a2798c72..adb3645a 100644
--- a/README.md
+++ b/README.md
@@ -46,20 +46,38 @@ We use GitHub Codespaces for our `inner-loop` and `outer-loop` Developer Experie
 
 ## Create a new Repo
 
+> If you are a member of the CSE-Labs org, skip this step
+
 - Click `Use this template`
   - Select `Create a new repository`
 
 ## Create a Codespace
 
-- Create a Codespace from the repo you created. You can use the same Codespace for any of the labs.
-
-> Note: make sure you create a codespace from the created repo, not the template repo.
+- If you are a member of the CSE-Labs org
+  - Create a Codespace from this repo
+- Otherwise
+  - Create a Codespace from the repo you created above
+- You can use the same Codespace for any of the labs
 
 - Click the `<> Code` button
   - Make sure the Codespaces tab is active
 - Click `Create Codespace on main`
 - After about 5 minutes, you will have a GitHub Codespace running with a complete Kubernetes Developer Experience!
 
+## Working Branch
+
+> This is required if you are using the CSE-Labs org
+
+- Create and push a working branch
+
+  ```bash
+
+  # MY_BRANCH is lower case GITHUB_USER
+  git checkout -b $MY_BRANCH
+  git push -u origin $MY_BRANCH
+
+  ```
+
 ## Environment variables
 
 Many of these labs use environment variables, using the export functionality. If you wish, you can edit the kic.env file to persist exported environment variables across terminal sessions. Just add the same "export FOO=BAR" lines to your kic.env file.