diff --git a/README.md b/README.md
index 2b44496dcfbe3b3dbd3c590570aa3f9cd0072fde..69dd7ea75671a0c415f2bfb89664b74ec2c6a03b 100644
--- a/README.md
+++ b/README.md
@@ -53,6 +53,14 @@ assignment number. You can run these commands from the shell container. These fu
 # build_kernel ASST0
 # test_kernel ASST0
 ```
+
+To fully evaluate youre kernel with the automated testing scripts you may use
+```
+# /run_assignment.sh ASST#
+```
+This will run `build_kernel` and `test_kernel` as well as evaluate the output produced by `test_kernel` (The raw output for build and test kernel can be found in /logs).
+
+
 If you would like to run the kernel normally (no scripts), once built, you can run the kernel
 ```
 # cd /os-compile
@@ -97,7 +105,8 @@ cd /os161-1.99/
 bmake
 bmake install
 ```
-User-level programs are installed under $OS161TOP/root/ in the bin, sbin, testbin and uw-testbin directories.
+User-level programs are installed under $OS161TOP/root/ in the bin, sbin, testbin and uw-testbin directories. This is done automatically
+by the build_kernel command.
 
 ## Running Linux userspace assignments
 To run the Linux userspace programs in the container, that are part of the progrmaming assignment, you must start the container using the `run.sh` script, which takes one argument -- the directory that holds your code for that userspace programming assignment, that is, the `c` files for the programming assignments. For example,