diff --git a/README.md b/README.md
index 84c87f2..a0123ce 100644
--- a/README.md
+++ b/README.md
@@ -195,9 +195,10 @@ which follows the immutable infrastructure paradigm.
 <details>
 <summary>What ways are you familiar with to deliver a software? What are the advantages and disadvantages of each method?</summary><br><b>
 
-  * Archive - collect all your app files into one archive (e.g. tar) and deliver it to the user.
-  * Package - depends on the OS, you can use your OS package format (e.g. in RHEL/Fefodra it's RPM) to deliver your software with a way to install, uninstall and update it using the standard packager commands
-  * Images - Either VM or container images where your package is included with everything it needs in order to run successfully.
+  * Source - Maintain build script within version control system so that user can build your app after cloning repository. Advantage: User can quickly checkout different versions of application. Disadvantage: requires build tools installed on users machine.
+  * Archive - collect all your app files into one archive (e.g. tar) and deliver it to the user. Advantage: Only tool needed is an unarchiver. Disadvantage: Requires repeating the same procedure when updating, not good if there are a lot of dependencies.
+  * Package - depends on the OS, you can use your OS package format (e.g. in RHEL/Fefodra it's RPM) to deliver your software with a way to install, uninstall and update it using the standard packager commands. Advantages: Package manager takes care of support for installation, uninstallation, updating and dependency management. Disadvantage: Requires managing package repository.
+  * Images - Either VM or container images where your package is included with everything it needs in order to run successfully. Advantage: everything is preinstalled, it has high degree of environment isolation. Disadvantage: Requires knowledge of building and optimizing images.
 </b></details>
 
 <details>
@@ -6295,7 +6296,7 @@ for i in range(1, 10):
 </summary><br><b>
 
 ```
-[for i in in range(1, 10)]
+[i for i in range(1, 10)]
 ```
 </b></details>
 
diff --git a/prepare_for_interview.md b/prepare_for_interview.md
index a22f4cc..35137f1 100644
--- a/prepare_for_interview.md
+++ b/prepare_for_interview.md
@@ -80,7 +80,7 @@ Starting a DevOps project is a good idea because:
 * It will make you practice coding
 * It will be something you can add to your resume and talk about with the interviewer
 * Depends on size and complexity, it can teach you something about design in general
-* Depends on adoption, it can you teach you about managing Open Source projects
+* Depends on adoption, it can teach you about managing Open Source projects
   
 Same here, don't overthink what your project should be about. Just go and build something :)
   
@@ -95,7 +95,7 @@ Better yet, ask a good friend/colleague to challenge you with some questions. Yo
   
 For those who attend technical meetups and conferences, it can be a great opportunity to chat with people from other companies on their interviewing process. But don't start with it, it can be quite awkward. Say at least hello first... (:
   
-Doing so can give you a lot of information on what to expect from an interview at some companies or how to how to better prepare.
+Doing so can give you a lot of information on what to expect from an interview at some companies or how to better prepare.
   
 ### Know your resume