Minor Spelling Changes

Minor Spelling Changes

Author: Ali-Yazdani

old-versions/V0.1/00a-Overview.md

@@ -96,7 +96,7 @@ it checks the software behavior under unexpected conditions and inputs.
 
 3. **Interactive analysis**
 
-   Also known as Interactive Application Security Testig (IAST) monitors the application while other systems interact with it and observe vulnerabilities. This is achieved via sensors or agents deploy with the application. The sensors can see the entire flow from HTTP request down to the executed code, tracing the data through the application. Similar to static analysis, it can test one component at a time, but not multiple components. However, if agents/sensors are deployed on all components, when they interact with eachother this could reveal vulnerabilities in each component used in the application. (Eg. for a microservice architecture, only the microservices that have agents/sensors attached will report vulnerabilities)
+   Also known as Interactive Application Security Testing (IAST) monitors the application while other systems interact with it and observe vulnerabilities. This is achieved via sensors or agents deploy with the application. The sensors can see the entire flow from HTTP request down to the executed code, tracing the data through the application. Similar to static analysis, it can test one component at a time, but not multiple components. However, if agents/sensors are deployed on all components, when they interact with eachother this could reveal vulnerabilities in each component used in the application. (Eg. for a microservice architecture, only the microservices that have agents/sensors attached will report vulnerabilities)
    ![Interactive analysis](/document/assets/images/iast_analysis.png)
 
 ---

old-versions/V0.1/01b-Linting-Code.md

@@ -28,7 +28,7 @@ Advanced static analysis tools typically deliver:
 - Out-of-the-box certification for use in the development of safety-critical applications.
 
 ### Issues with Linters
-+ Not every language has "quality" standard linter tools available, each framwork usually has one or several linters.
++ Not every language has "quality" standard linter tools available, each framework usually has one or several linters.
 + Different versions or configurations can lead to different results.
 + Since some linters are very verbose and information overload can lead to focusing on "unimportant" issues.
 
@@ -40,4 +40,4 @@ You can perform it in the **pre-commit** phase, so locally before actually commi
 
 ### References
 
-+ [Preforce](https://www.perforce.com/blog/qac/what-lint-code-and-why-linting-important)
++ [Preforce](https://www.perforce.com/blog/qac/what-lint-code-and-why-linting-important)

old-versions/V0.1/02f-Container-Vulnerability-Scanning.md

@@ -17,7 +17,7 @@ As containers become an almost ubiquitous method of packaging and deploying appl
 ### Where and When to use Container Scanner? 
 <img align="center" src="/document/assets/images/Dev-process.png">  
 
-You can use it at the build phase when you're actually building for instance a Dockerfile and looking at the resulting image that you're creating. Another location to perform container scanning would be when you push a container to the registry or when you pull a container from a registry. However, a good approach is scanning before pushing into a trusted container registry then you can say we have a container registry with a scanned version of all images and for deploying in production you can pull from this trusted container registry. (Plase take look into the following image)
+You can use it at the build phase when you're actually building for instance a Dockerfile and looking at the resulting image that you're creating. Another location to perform container scanning would be when you push a container to the registry or when you pull a container from a registry. However, a good approach is scanning before pushing into a trusted container registry then you can say we have a container registry with a scanned version of all images and for deploying in production you can pull from this trusted container registry. (Please take look into the following image)
 
 <img align="center" src="/document/assets/images/container-security-pipeline.png">