Update README.md

contributions/demo/week2/mqnguyen-golman/README.md

@@ -2,7 +2,7 @@
 
 ## Title
 
-Continuous integretion testing of node and service availability of promox instances
+Continuous integration testing of node and service availability of promox instances
 
 ## Names and KTH ID
 
@@ -37,4 +37,4 @@ In case we run into difficulties we deem unfeasible to overcome (the environment
 
 **Relevance**
 
-We believe this is very rare compared to more conventional integration tests that may, for example, include a frontend and backend the the interactions between those two components. We also believe it is comparatively complex as it involves a lot of steps both in terms of setting up the environment and performing the tests. It also seem to fulfill a task that frequently would need to be performed manually by a system administrator otherwise. It is of course highly relevant to DevOps in general as it involves several CI tools such as Jenkins.
+We believe this is very rare compared to more conventional integration tests that may, for example, include a frontend and backend the the interactions between those two components. We also believe it is comparatively complex as it involves a lot of steps both in terms of setting up the environment and performing the tests. It also seem to fulfill a task that frequently would need to be performed manually by a system administrator otherwise. It is of course highly relevant to DevOps in general as it involves several CI tools such as Jenkins.