linode · Jskobos · Feb 2, 2018 · Feb 2, 2018
diff --git a/...ference/custom-kernels-distros/install-a-custom-distribution-on-a-xen-linode.md b/...ference/custom-kernels-distros/install-a-custom-distribution-on-a-xen-linode.md
@@ -17,7 +17,7 @@ title: Install a Custom Distribution on a Xen Linode
 If you'd like to run a Linux distribution on your Linode that isn't available from our distribution list, you can do so by following these instructions. This guide is handy for people who prefer distributions that aren't heavily used in the community, or for those interested in creating a highly customized Linux environment and porting it to their Linode.
 
 {{< note >}}
-This guide is intended for Linodes using our older Xen hypervisor. To installl a custom distribution on a new KVM Linode, see [this guide](/docs/tools-reference/custom-kernels-distros/install-a-custom-distribution-on-a-linode).
+This guide is intended for Linodes using our older Xen hypervisor. To install a custom distribution on a new KVM Linode, see [this guide](/docs/tools-reference/custom-kernels-distros/install-a-custom-distribution-on-a-linode).
 {{< /note >}}
 
 ## Creating the Virtual Machine

diff --git a/docs/tools-reference/custom-kernels-distros/install-coreos-on-your-linode.md b/docs/tools-reference/custom-kernels-distros/install-coreos-on-your-linode.md
@@ -25,7 +25,7 @@ CoreOS Container Linux is now available for deployment from the Linode Manager.
 
 [CoreOS](https://coreos.com/) is a container-centric Linux distribution designed for clustered systems running in the cloud. With user applications running inside containers, the host system itself provides minimal functionality. This guide details installing CoreOS on a **KVM** Linode. If you're running a Xen Linode, you can [upgrade](/docs/platform/kvm-reference/#how-to-enable-kvm), but it is currently not possible to install CoreOS on a Xen Linode.
 
-CoreOS is not officially supported by Linode so there are limitations to using it in comparision to the Linux images provided in the Linode Manager.
+CoreOS is not officially supported by Linode so there are limitations to using it in comparison to the Linux images provided in the Linode Manager.
 
 *   The CoreOS installer will create a partition table on the disk image which will interfere with the [Linode Backup](/docs/platform/backup-service) service because the disk image will not be directly mountable.
 

diff --git a/...ls-reference/custom-kernels-distros/run-a-custom-compiled-kernel-with-pvgrub.md b/...ls-reference/custom-kernels-distros/run-a-custom-compiled-kernel-with-pvgrub.md
@@ -95,7 +95,7 @@ Once your configuration options are set, exit the configuration interface and an
 
         mv /boot/vmlinuz /boot/vmlinuz-3.19.3-custom
 
-3.  Create an `initrd` file. Aagain, adjust the filename to match your current kernel version:
+3.  Create an `initrd` file. Again, adjust the filename to match your current kernel version:
 
         mkinitrd -o initrd-3.19.3-custom.img
 

diff --git a/docs/tools-reference/tools/introduction-to-vim-customization.md b/docs/tools-reference/tools/introduction-to-vim-customization.md
@@ -21,12 +21,11 @@ external_resources:
  - '[The Vim Tips Wiki](http://vim.wikia.com/wiki/Vim_Tips_Wiki)'
 ---
 
-
-![Vim_banner](/docs/assets/Vim_Customization.jpg)
+![Introduction to Vim Customization](/docs/assets/Vim_Customization.jpg)
 
 ## What Is Vim?
 
-Vim is one of a handful of text editors ubiquitous in nearly all Unix systems. While an initial learning curve is unavoidable, Vim aims to be a hyperefficient text editor and provides an extensive plug-in system which can be configured to user preferences. It also supports  hundreds of programming languages and file extentions.
+Vim is one of a handful of text editors ubiquitous in nearly all Unix systems. While an initial learning curve is unavoidable, Vim aims to be a hyperefficient text editor and provides an extensive plug-in system which can be configured to user preferences. It also supports  hundreds of programming languages and file extensions.
 
 This guide details the configuration of the Vim text editor and aims at those who are interested in taking the next step into customization. An array of methods for customizing Vim's execution of certain tasks and response to user input will be introduced, along with a plug-in management system.
 

diff --git a/docs/tools-reference/tools/schedule-tasks-with-cron.md b/docs/tools-reference/tools/schedule-tasks-with-cron.md
@@ -80,7 +80,7 @@ These represent the interval of repetition with which tasks are processed. In or
 
 -   The `/` operator "steps through" or "skips" a specified units. Therefore `*/3` in the hour field, will run the specified job, at 12:00 am, 3:00am, 6:00am, 9:00am, 12:00pm, 3:00pm, 6:00pm, and 9:00pm. A `*/3` in the "day of month" field, runs the given task on the 3rd, 6th, 9th, 12th, 15th, 18th, 21st, and 29th of every month.
 -   The `,` operator allows you to specify a list of times for repetition. Comma separated lists of times must not contain a space.
--   The `-` operator specifies a range of values. `2-4` in the month field will run a task in Feburary, March, and April. `1-5` in the day of week field will run a task every weekday.
+-   The `-` operator specifies a range of values. `2-4` in the month field will run a task in February, March, and April. `1-5` in the day of week field will run a task every weekday.
 
 Fields in crontab entries are separated by spaces. If you are using special cron operators, be particularly careful to avoid unintentional spaces in your command.
 

diff --git a/docs/troubleshooting/rescue-and-rebuild.md b/docs/troubleshooting/rescue-and-rebuild.md
@@ -95,7 +95,7 @@ Now you can read and write to files on the mounted disk.
 
 Change root is the process of changing your working root directory. When you change root (chroot) to your Linode root disk, you will be able to run commands as though you are logged into that system.
 
-Chroot will allow you to change user passwords, remove/install packages, and do other system maintanance and recovery tasks.
+Chroot will allow you to change user passwords, remove/install packages, and do other system maintenance and recovery tasks.
 
 Before you can use chroot, you need to mount your root disk with execute permissions:
 

diff --git a/docs/uptime/analytics/google-analytics-for-websites.md b/docs/uptime/analytics/google-analytics-for-websites.md
@@ -156,7 +156,7 @@ Should you decide to disable the demographics feature at a later date, simply re
 Change the `.html` ending to match the ending of your website's files.
 {{< /note >}}
 
-8.  To check that the code has been successfully inserted into your `.html` files, you can either open up your website in your browser and view the source code, or view a file in your terminal. The folllowing should appear in conjunction to your `<head>` tag:
+8.  To check that the code has been successfully inserted into your `.html` files, you can either open up your website in your browser and view the source code, or view a file in your terminal. The following should appear in conjunction to your `<head>` tag:
 
     {{< file-excerpt "/var/www/example.com/public_html/index.html" >}}
 <head><script type="text/javascript" src="javascript/ga.js"></script>

diff --git a/docs/uptime/analytics/zipkin-server-configuration-using-docker-and-mysql.md b/docs/uptime/analytics/zipkin-server-configuration-using-docker-and-mysql.md
@@ -19,7 +19,7 @@ external_resources:
 
 [Zipkin](http://zipkin.io/) is a used for capturing timing data, it also has a centralized repository, and a microweb server that allows you to display, and search through spans and traces of your distributed programs or websites.
 
-We can configure Zipkin by [deploying it in a Docker container](http://zipkin.io/pages/quickstart). Using this approach, we can match the latest version of Zipkin by just pulling down the latest images. You can Isolate the Docker service and dependencies to just the container(s), and chose where you want your data to persist. Most importantly, by using Docker, you can spend more time focused on data anlysis, instead of spending time on configuring a Zipkin as a service.
+We can configure Zipkin by [deploying it in a Docker container](http://zipkin.io/pages/quickstart). Using this approach, we can match the latest version of Zipkin by just pulling down the latest images. You can Isolate the Docker service and dependencies to just the container(s), and chose where you want your data to persist. Most importantly, by using Docker, you can spend more time focused on data analysis, instead of spending time on configuring a Zipkin as a service.
 
 ## Before You Begin
 
@@ -98,7 +98,7 @@ The Docker service will manage your containers, the container's host, Zipkin ser
 
 Docker is in charge of starting and stopping these services automatically when the host system is rebooted. it'll help us to map the ports from the container to the host's ports and it'll manage exporting the MySQL database files onto the host system. Docker can check to see if the container has failed, and restart it for us too. The host is in charge of running the actual Docker service and setting the firewall correctly.
 
-Notice that the Zipkin container will expose port 9411 for its service, and the MySQL container will expose port 3306. We'll use the Docker-compose yaml files to forward port 9411 to the host's port 9411, so that the container will be accesible on the internet.
+Notice that the Zipkin container will expose port 9411 for its service, and the MySQL container will expose port 3306. We'll use the Docker-compose yaml files to forward port 9411 to the host's port 9411, so that the container will be accessible on the internet.
 
 #### Zipkin Server Firewall Concepts