Guaris tar qa

docs/applications/big-data/big-data-in-the-linode-cloud-streaming-data-processing-with-apache-storm.md

@@ -256,7 +256,7 @@ Creating a new Storm cluster involves four main steps, some of which are necessa
 
 ### Create a Zookeeper Image
 
-A *Zookeeper image* is a master disk image with all necessary Zookeeper softwares and libraries installed. We'll create our using [Linode Images](/docs/platform/linode-images) The benefits of using a Zookeeper image include:
+A *Zookeeper image* is a master disk image with all necessary Zookeeper software and libraries installed. We'll create our using [Linode Images](/docs/platform/linode-images) The benefits of using a Zookeeper image include:
 
 -  Quick creation of a Zookeeper cluster by simply cloning it to create as many nodes as required, each a perfect copy of the image
 -  Distribution packages and third party software packages are identical on all nodes, preventing version mismatch errors

docs/applications/big-data/how-to-scrape-a-website-with-beautiful-soup.md

@@ -146,7 +146,7 @@ rec = {
 
         'pid': result['data-pid']
 
-4.  Other data attributes may be nested deeper in the HTML strucure, and can be accessed using a combination of dot and array notation. For example, the date a result was posted is stored in `datetime`, which is a data attribute of the `time` element, which is a child of a `p` tag that is a child of `result`. To access this value use the following format:
+4.  Other data attributes may be nested deeper in the HTML structure, and can be accessed using a combination of dot and array notation. For example, the date a result was posted is stored in `datetime`, which is a data attribute of the `time` element, which is a child of a `p` tag that is a child of `result`. To access this value use the following format:
 
         'date': result.p.time['datetime']
 

docs/applications/configuration-management/creating-your-first-chef-cookbook.md

@@ -131,7 +131,7 @@ end
 
         knife cookbook upload lamp-stack
 
-5.  Add the recipe to a node's run-list, replaceing `nodename` with your chosen node's name:
+5.  Add the recipe to a node's run-list, replacing `nodename` with your chosen node's name:
 
         knife node run_list add nodename "recipe[lamp-stack::apache]"
 

docs/applications/configuration-management/learn-how-to-install-ansible-and-run-playbooks.md

@@ -250,7 +250,7 @@ The following playbooks are for learning purposes only, and will NOT result in a
 
 3.  Write a playbook that creates a new normal user, adds in our public key, and adds the new user to the `sudoers` file.
 
-    We're introducing a new aspect of Ansible here: *variables*. Note the `vars:` entry and the `NORMAL_USER_NAME` line. You'll notice that it is reused twice in the file so that we only have to change it once. Replace `yourusername` with your choosen username, `localusername` in the path for the `authorized_key`, and the password hash.
+    We're introducing a new aspect of Ansible here: *variables*. Note the `vars:` entry and the `NORMAL_USER_NAME` line. You'll notice that it is reused twice in the file so that we only have to change it once. Replace `yourusername` with your chosen username, `localusername` in the path for the `authorized_key`, and the password hash.
 
     {{< file "initialize_basic_user.yml" yaml >}}
 ---

docs/applications/configuration-management/vagrant-linode-environments.md

@@ -307,7 +307,7 @@ With the Vagrantfile configured, and scripts and files created, it's now time to
 
          * apache2 is running
 
-4.  To see that the environment is accesible online, check for the IP address:
+4.  To see that the environment is accessible online, check for the IP address:
 
         hostname -i