diff --git a/course4/week3-ungraded-labs/C4_W3_Lab_2_TFX_Custom_Components.ipynb b/course4/week3-ungraded-labs/C4_W3_Lab_2_TFX_Custom_Components.ipynb
index 9ba364261..5a6adc708 100644
--- a/course4/week3-ungraded-labs/C4_W3_Lab_2_TFX_Custom_Components.ipynb
+++ b/course4/week3-ungraded-labs/C4_W3_Lab_2_TFX_Custom_Components.ipynb
@@ -720,7 +720,7 @@
       "source": [
         "### Standard ExampleGen code\n",
         "\n",
-        "TFX is open source so the code for standard components can easily be found the public [repo](https://github.com/tensorflow/tfx/tree/89d3cb6c59acd0d487916bff703711815f1506b5/tfx). We placed links in the following sections of the actual files that you'll be modifying/overriding in case you want to compare what was changed for your custom ExampleGen. \n",
+        "TFX is open source so the code for standard components can easily be found in the public [repo](https://github.com/tensorflow/tfx/tree/89d3cb6c59acd0d487916bff703711815f1506b5/tfx). We placed links in the following sections of the actual files that you'll be modifying/overriding in case you want to compare what was changed for your custom ExampleGen. \n",
         "\n",
         "The class heirarchy for these components is pretty deep but in summary, you will only need to modify three:\n",
         "\n",
@@ -1055,4 +1055,4 @@
       ]
     }
   ]
-}
\ No newline at end of file
+}
diff --git a/course4/week3-ungraded-labs/C4_W3_Lab_3_TFS_Model_Versioning/README.md b/course4/week3-ungraded-labs/C4_W3_Lab_3_TFS_Model_Versioning/README.md
index b051d0db8..a313acbfb 100644
--- a/course4/week3-ungraded-labs/C4_W3_Lab_3_TFS_Model_Versioning/README.md
+++ b/course4/week3-ungraded-labs/C4_W3_Lab_3_TFS_Model_Versioning/README.md
@@ -159,7 +159,7 @@ To test the different model versions you can use the `dog_example.json` file tha
 
 Since you defined labels for the versions of the models you can consume them either by using numerical versioning or labels.
 
-Begin by sending a `POST` request to version 1 of the model:
+Begin by sending a `POST` request to version 2 of the model:
 
 ```bash
 curl -X POST http://localhost:8501/v1/models/animals/versions/2:predict \
diff --git a/course4/week3-ungraded-labs/C4_W3_Lab_4_Github_Actions/README.md b/course4/week3-ungraded-labs/C4_W3_Lab_4_Github_Actions/README.md
index 9b8674d56..44a84d24b 100644
--- a/course4/week3-ungraded-labs/C4_W3_Lab_4_Github_Actions/README.md
+++ b/course4/week3-ungraded-labs/C4_W3_Lab_4_Github_Actions/README.md
@@ -134,12 +134,12 @@ In the next part you need to define all of the jobs than will run when this acti
     steps:
       -
         name: Checkout
-        uses: actions/checkout@v2
+        uses: actions/checkout@v4
       - 
         name: Set up Python
-        uses: actions/setup-python@v2
+        uses: actions/setup-python@v4
         with:
-          python-version: '3.7.7'
+          python-version: '3.8'
       - 
         name: Install dependencies
         run: |
@@ -155,16 +155,16 @@ In the next part you need to define all of the jobs than will run when this acti
 Finally you need to specify the `steps` for this action to be completed. This is a sequence of commands to achieve the functionality you strive for.  `steps` have several values associated such as:
 - `name`: The name of the step.
 
-- `uses`: You can specify an already existing `Action` as an step on one of your own. This is pretty cool because it allows for reutilization of Actions. 
+- `uses`: You can specify an already existing `Action` as a step on one of your own. This is pretty cool because it allows for reutilization of Actions. 
 - `run`: Instead of using an existing Action you might need to run a command. Since you are using `bash` inside a Linux VM, these commands should follow the correct syntax.
 - `with`: You might need to specify some additional values. This field is for such cases.
 
 
 Let's understand every step in order:
 
-- The first step uses the `actions/checkout@v2` Action. This is usually included in every Action since it allows GitHub to access or check-out your repo.
+- The first step uses the `actions/checkout@v4` Action. This is usually included in every Action since it allows GitHub to access or check-out your repo.
 
-- Now that your repo has been checked-out, you need to set an environment capable of running your Python code. To accomplish this the `actions/setup-python@v2` Actions is used while specifying the desired Python version.
+- Now that your repo has been checked-out, you need to set an environment capable of running your Python code. To accomplish this the `actions/setup-python@v4` Actions is used while specifying the desired Python version.
 - Having a Python supported environment it is time to install of the dependencies that your application needs. You can do so by using upgrading `pip` and then using it to install the dependencies listed in the `requirements.txt` file.
 - Finally you can run your unit tests by simply using the `pytest` command. Notice that you needed to `cd` into the `app` directory first.