diff --git a/.DS_Store b/.DS_Store
deleted file mode 100644
index d90aace..0000000
Binary files a/.DS_Store and /dev/null differ
diff --git a/unit06_trust_dig_cert/lab/README.MD b/unit06_trust_dig_cert/lab/README.MD
index a56998d..f26e658 100644
--- a/unit06_trust_dig_cert/lab/README.MD
+++ b/unit06_trust_dig_cert/lab/README.MD
@@ -500,10 +500,25 @@ Run the code and answer the following questions:
 * Which key (public or private key) is used to verify the signature?
 * Which key (public or private key) is used to verify the signature?
 
+# AWS Lab
+Within digital signatures, we have two main signatures: RSA, ECDSA and EdDSA. In AWS, we can implement RSA (with PSS) and ECDSA.
+
+## RSA PSS Signatures
+In digital signing, we use our private key to sign for a message, and then the proof of signing is done with our public key. This happens for a Bitcoin transaction, and where we take the private key from our wallet and then sign for a transaction. The public key is then used to prove that the user signing the transaction. While Bitcoin uses ECDSA, we can also use RSA signing. A common method is RSASSA_PSS_SHA_256.
+
+![image info](https://asecuritysite.com/public/rsa_sig.png)
+
+Undertake the lab [here](https://asecuritysite.com/aws/lab09).
+
+## ECDSA Signatures
+In digital signing, we use our private key to sign for a message, and then the proof of signing is done with our public key. This happens for a Bitcoin transaction, and where we take the private key from our wallet and then sign for a transaction. The public key is then used to prove that the user signing the transaction. 
+
+![image info](https://asecuritysite.com/public/kms_20.png)
+
+Undertake the lab [here](https://asecuritysite.com/aws/lab05).
 
 
-
-## What I should have learnt from this lab?
+## What should I have learned from this lab?
 The key things learnt:
 
 * Understand how digital certificates are generated and ported onto systems.
diff --git a/unit06_trust_dig_cert/lab/~$w_lab06.docx b/unit06_trust_dig_cert/lab/~$w_lab06.docx
new file mode 100644
index 0000000..827a495
Binary files /dev/null and b/unit06_trust_dig_cert/lab/~$w_lab06.docx differ
diff --git a/unit06a_mini_project/README.md b/unit06a_mini_project/README.md
index b3f9be5..405ef7f 100644
--- a/unit06a_mini_project/README.md
+++ b/unit06a_mini_project/README.md
@@ -124,12 +124,12 @@ The following is some sample code you can test your hashes against:
 import hashlib;
 import passlib.hash;
 
-string="password"
-print "General Hashes"
-print "MD5:"+hashlib.md5(string).hexdigest()
-print "SHA1:"+hashlib.sha1(string).hexdigest()
-print "SHA256:"+hashlib.sha256(string).hexdigest()
-print "SHA512:"+hashlib.sha512(string).hexdigest()
+string="password".encode()
+print ("General Hashes")
+print ("MD5:"+hashlib.md5(string).hexdigest())
+print ("SHA1:"+hashlib.sha1(string).hexdigest())
+print ("SHA256:"+hashlib.sha256(string).hexdigest())
+print ("SHA512:"+hashlib.sha512(string).hexdigest())
 ```
 
 To test your PBKDF2 code, you will have to take the salt generated randomly from your Web page and copy it. For example:
diff --git a/unit06a_mini_project/lab_mini_project.docx b/unit06a_mini_project/lab_mini_project.docx
index f18a6f9..ef0717d 100644
Binary files a/unit06a_mini_project/lab_mini_project.docx and b/unit06a_mini_project/lab_mini_project.docx differ
diff --git a/unit06a_mini_project/lab_mini_project.pdf b/unit06a_mini_project/lab_mini_project.pdf
index eae9801..03a111c 100644
Binary files a/unit06a_mini_project/lab_mini_project.pdf and b/unit06a_mini_project/lab_mini_project.pdf differ
diff --git a/unit06a_mini_project/~$b_mini_project.docx b/unit06a_mini_project/~$b_mini_project.docx
new file mode 100644
index 0000000..1215360
Binary files /dev/null and b/unit06a_mini_project/~$b_mini_project.docx differ