Merge pull request leonjza#2 from veronicapablo/master

Fixed frida.md

course/2-chapter-2/frida.md

@@ -32,7 +32,7 @@ The Frida project is pretty large, and there are many moving parts to it.
 
 The first, and most important part is the Frida core, written in C. This component is responsible for injecting a JavaScript engine like V8 or Duktape into the target process and runs the JavaScript that you wrote in the target process.
 
-The the next component would be the Frida language bindings. It is possible to communicate with the Frida core using anyone one of the following languages; C, Python, Node Swift and .NET. For this workshop we will be using the Python bindings, but really you are free to choose whichever you prefer.
+The next component would be the Frida language bindings. It is possible to communicate with the Frida core using anyone one of the following languages; C, Python, Node Swift and .NET. For this workshop we will be using the Python bindings, but really you are free to choose whichever you prefer.
 
 Next, there are language runtime bridges (or gum). These bridges make use of metadata rich runtimes such as Objective-C and Java on mobile devices that allows you to instrument these higher-level languages without the need to know the intricacies of the target runtimes themselves. While Objective-C and Java bridges are part of Frida, community bridges for runtimes like Swift and Mono (.NET) also exist.
 
@@ -42,7 +42,7 @@ Finally, there are a set of command line tools that make use of the Python bindi
 
 Frida can operate in three primary modes:
 
-- Injected (how were are going to use it most of the time)
+- Injected (how we're going to use it most of the time)
 - Embedded (basically a shared library that you can make part of a project)
 - Preload (a combination of embedded mode with JavaScript already built to autonomously instrument applications)
 

course/2-chapter-2/javascript.md

@@ -12,7 +12,7 @@ From the documentation one can quickly see the wide range of features Frida has.
 
 ## repl
 
-The Frida REPL can autocomplete most of the Frida modules as well. This makes prototyping very fast from inside the Frida REPL. For example, with the `frida` tool attached to the already running `sleep_test` program, we can start playing with the API right away.
+The Frida REPL can autocomplete most of the Frida modules as well. This makes prototyping very fast from inside the Frida REPL. For example, with the `frida` tool attached to the already running `pew` program, we can start playing with the API right away.
 
 ?> Try and hit `TAB` as often as you can, there are plenty of places where it works!
 
@@ -22,7 +22,7 @@ The Frida REPL can autocomplete most of the Frida modules as well. This makes pr
 ```
 
 ```text
-[Local::sleep_test]-> Process.getModuleByName("libc-2.30.so");
+[Local::pew]-> Process.getModuleByName("libc-2.30.so");
 {
     "base": "0x7fe5d9644000",
     "name": "libc-2.30.so",
@@ -32,4 +32,4 @@ The Frida REPL can autocomplete most of the Frida modules as well. This makes pr
 [Local::pew]->
 ```
 
-All of this is happening while the target process, `sleep_test` is still running...
+All of this is happening while the target process, `pew` is still running...