Merge pull request #8 from httpdigest/master

Fix typos and grammar in chapter 1 and 2

Author: lwjglgamedev

chapter1/chapter1.md

@@ -1,26 +1,26 @@
 # First steps
 
-In this book we will learn the principal techniques involved in developing 3D games. We will develop our samples in Java and we will use the Java Lightweight Game Library ([LWJGL](http://www.lwjgl.org/)). The LWJGL library enables the access to low-level APIs (Application Programming Interface) such as OpenGL.
+In this book we will learn the principal techniques involved in developing 3D games. We will develop our samples in Java and we will use the Lightweight Java Game Library ([LWJGL](http://www.lwjgl.org/)). The LWJGL library enables the access to low-level APIs (Application Programming Interface) such as OpenGL.
 
-LWJGL is a low level API that acts like a wrapper around OpenGL. If your idea is to start creating 3D games in a short period of time maybe you should consider other alternatives like  [JmonkeyEngine]. By using this low level API you will have to go through many concepts and write lots of lines of code before you see the results. The benefit of doing this way is that you will get a much better understanding about 3D graphics and also you can get a better control.
+LWJGL is a low level API that acts like a wrapper around OpenGL. If your idea is to start creating 3D games in a short period of time maybe you should consider other alternatives like  [JmonkeyEngine]. By using this low level API you will have to go through many concepts and write lots of lines of code before you see the results. The benefit of doing it this way is that you will get a much better understanding of 3D graphics and also you can get better control.
 
-As said in the previous paragraphs we will be using Java for this book. We will be using Java 8, so you need to download Java SDK from Oracle’s pages. Just choose the installer that suits your Operative System and install it. This book assumes that you have a moderate understanding of the Java language.
+As said in the previous paragraphs we will be using Java for this book. We will be using Java 8, so you need to download the Java SDK from Oracle’s pages. Just choose the installer that suits your Operating System and install it. This book assumes that you have a moderate understanding of the Java language.
 
-The source code that accompanies this book has been developed using the Netbeans IDE. You can download the latest version of that IDE from [https://netbeans.org/](https://netbeans.org/). In order to execute Netbeans you only need the Java SE version but remember to download the version that suits with your JDK version (32 bits or 64 bits).
+The source code that accompanies this book has been developed using the Netbeans IDE. You can download the latest version of that IDE from [https://netbeans.org/](https://netbeans.org/). In order to execute Netbeans you only need the Java SE version but remember to download the version that corresponds to your JDK version (32 bits or 64 bits).
 
 ![Netbeans download](netbeans_download.png)
 
-For building our samples we will be using [Maven](https://maven.apache.org/). Maven is already integrated in Netbeans and you can directly open the different samples from Netbeans, just open the folder that contains the chapter sample and Netbeans will detect that it is a maven project.
+For building our samples we will be using [Maven](https://maven.apache.org/). Maven is already integrated in Netbeans and you can directly open the different samples from Netbeans. Just open the folder that contains the chapter sample and Netbeans will detect that it is a maven project.
 
 ![Maven projects](maven_projecs.png)
 
 Maven builds projects based on an XML file named ```pom.xml``` (Project Object Model) which manages project dependencies (the libraries you need to use) and the steps to be performed during the build process. Maven follows the principle of convention over configuration, that is, if you stick to the standard project structure and naming conventions the configuration file does not need to explicitly say where source files are or where compiled classes should be located.
 
 This book does not intend to be a maven tutorial, so please find the information about it in the web in case you need it.  The source code folder defines a parent project which defines the plugins to be used and collects the versions of the libraries employed. 
 
-LWJGL 3.1 introduced some changes in the way that the project is built. Now the base code is much more modular, and we can be more selective in the packages that we want to use insetad of using a giant monolithic jar file. This comes at a cost, you now need to carefully specif the dependencies one by one, but the [download](https://www.lwjgl.org/download) page includes a fancy script that generates the pom file for you. In our case, we will just be using GLFW and OpenGL bindings. You can check what the pom file looks like in the source code.
+LWJGL 3.1 introduced some changes in the way that the project is built. Now the base code is much more modular, and we can be more selective in the packages that we want to use instead of using a giant monolithic jar file. This comes at a cost: You now need to carefully specify the dependencies one by one. But the [download](https://www.lwjgl.org/download) page includes a fancy script that generates the pom file for you. In our case, we will just be using GLFW and OpenGL bindings. You can check what the pom file looks like in the source code.
 
-LWJGL platform dependency already takes care of unpacking native libraries for your platform, so there's no need to use other plugings (such as ```mavennatives```). We just need to set up three profiles to set a property that will configure LWJGL platform. The profiles will set up the correct values of that property for Windows, Linux and Mac OS families.
+The LWJGL platform dependency already takes care of unpacking native libraries for your platform, so there's no need to use other plugings (such as ```mavennatives```). We just need to set up three profiles to set a property that will configure the LWJGL platform. The profiles will set up the correct values of that property for Windows, Linux and Mac OS families.
 
 ```xml
 	<profiles>
@@ -71,20 +71,18 @@ Inside each project, the LWJGL platform dependency will use the correct property
         </dependency>
 ```
 
-Besides that, every project generates a runnable jar (one that can be executed by typing java -jar name_of_the_jar.jar). This is achieved by suing the maven-jar-plugin which creates a jar with a ```MANIFEST.MF``` file with the correct values. The most important attribute for that file is the ```Main-Class``` one, which sets the entry point for the program. In addition, all the dependencies are set as entries in the ```Class-Path``` attribute for that file. In order to execute it in another computer, you just need to copy the main jar file and the lib directory (with all the jars included there) which are located under the target directory.
+Besides that, every project generates a runnable jar (one that can be executed by typing java -jar name_of_the_jar.jar). This is achieved by using the maven-jar-plugin which creates a jar with a ```MANIFEST.MF``` file with the correct values. The most important attribute for that file is ```Main-Class```, which sets the entry point for the program. In addition, all the dependencies are set as entries in the ```Class-Path``` attribute for that file. In order to execute it on another computer, you just need to copy the main jar file and the lib directory (with all the jars included there) which are located under the target directory.
 
 When you execute the samples from Netbeans you need to specify the directory where the Java Virtual Machine will look for native libraries. This is done with the command line property: ```“-Djava.library.path”``` which should be set to: ```“-Djava.library.path="target\natives”```. This is done automatically for you in the ```nbactions.xml``` file. In case you want to change it or learn how to do it manually, right click in your project and select “Properties”. In the dialog that is shown select “Run” category and set the correct value for VM Options.
 
 ![VM Settings](vm_settings.png) 
 
 **The source code of this book is published in [GitHub](https://github.com/lwjglgamedev/lwjglbook).**
 
-Chapter 1 source code is taken directly from the getting started sample in the LWJGL site ([http://www.lwjgl.org/guide](http://www.lwjgl.org/guide)). You will see that we are not using Swing or JavaFX as our GUI library. Instead of that we are using [GLFW](www.glfw.org) which is a library to handle GUI components (Windows, etc.) and events (key presses, mouse movements, etc.) with an Open GL Context attached in a straight forward way. Previous versions of LWJGL provided a custom GUI API but, for LWJGL 3, GLFW is the preferred windowing API.
+Chapter 1 source code is taken directly from the getting started sample in the LWJGL site ([http://www.lwjgl.org/guide](http://www.lwjgl.org/guide)). You will see that we are not using Swing or JavaFX as our GUI library. Instead of that we are using [GLFW](www.glfw.org) which is a library to handle GUI components (Windows, etc.) and events (key presses, mouse movements, etc.) with an OpenGL context attached in a straightforward way. Previous versions of LWJGL provided a custom GUI API but, for LWJGL 3, GLFW is the preferred windowing API.
 
-The samples source code is very well documented and straight forward so we won’t repeat the comments here. 
+The samples source code is very well documented and straightforward so we won’t repeat the comments here.
 
-If you have your environment correctly set up you should be execute it and see a window with red background.
+If you have your environment correctly set up you should be able to execute it and see a window with a red background.
 
 ![Hello World](hello_world.png)
-
-