diff --git a/docs/tools-reference/custom-kernels-distros/install-a-custom-distribution-on-a-xen-linode.md b/docs/tools-reference/custom-kernels-distros/install-a-custom-distribution-on-a-xen-linode.md
index d0ff18e60dd..b6dc52c1901 100644
--- a/docs/tools-reference/custom-kernels-distros/install-a-custom-distribution-on-a-xen-linode.md
+++ b/docs/tools-reference/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
index 2b8660a00d1..fda9dbe0e12 100644
--- 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/docs/tools-reference/custom-kernels-distros/run-a-custom-compiled-kernel-with-pvgrub.md b/docs/tools-reference/custom-kernels-distros/run-a-custom-compiled-kernel-with-pvgrub.md
index 1b0a6b60987..8cf0140d492 100644
--- a/docs/tools-reference/custom-kernels-distros/run-a-custom-compiled-kernel-with-pvgrub.md
+++ b/docs/tools-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
old mode 100755
new mode 100644
index 8be51db84e6..0ff13d71f79
--- 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)'
---
-
-
+
## 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
index c06bd514d02..2562403cc92 100644
--- 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
index e4411b2e571..ee18c34167b 100644
--- 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
index 70716b294b3..876481a742b 100644
--- 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 `` 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 `` tag:
{{< file-excerpt "/var/www/example.com/public_html/index.html" >}}
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
index 58a3bcb1d6b..e3788c1c981 100644
--- 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
diff --git a/docs/uptime/loadbalancing/use-nginx-as-a-front-end-proxy-and-software-load-balancer.md b/docs/uptime/loadbalancing/use-nginx-as-a-front-end-proxy-and-software-load-balancer.md
index 405ce2d0fa1..45a111d9804 100644
--- a/docs/uptime/loadbalancing/use-nginx-as-a-front-end-proxy-and-software-load-balancer.md
+++ b/docs/uptime/loadbalancing/use-nginx-as-a-front-end-proxy-and-software-load-balancer.md
@@ -2,7 +2,7 @@
author:
name: Linode
email: docs@linode.com
-description: 'Use Nginx as a Front-end Proxy and Software Load-Balancer.'
+description: 'Use NGINX as a Front-end Proxy and Software Load-Balancer.'
keywords: ["apache", "nginx", "proxy", "load balancer", "load balancing", "web server", "http", "use nginx as proxy", "use nginx as load-balancer", "front-end proxy", "cluster"]
license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
aliases: ['web-servers/nginx/configuration/front-end-proxy-and-software-load-balancing/','websites/loadbalancing/Use-Nginx-for-Proxy-Services-and-Software-Load-Balancing/','uptime/loadbalancing/use-nginx-for-proxy-services-and-software-load-balancing/index.cfm/','uptime/loadbalancing/use-nginx-for-proxy-services-and-software-load-balancing/', 'uptime/loadbalancing/how-to-use-nginx-as-a-front-end-proxy-server-and-software-load-balancer/']
@@ -10,48 +10,48 @@ modified: 2017-03-23
modified_by:
name: Linode
published: 2010-05-11
-title: 'Use Nginx as a Front-end Proxy and Software Load Balancer'
+title: 'Use NGINX as a Front-end Proxy and Software Load Balancer'
external_resources:
- - '[nginx Proxy Module](http://wiki.nginx.org/NginxHttpProxyModule)'
+ - '[NGINX Proxy Module](http://wiki.nginx.org/NginxHttpProxyModule)'
- '[HTTP Upstream Module](http://wiki.nginx.org/NginxHttpUpstreamModule)'
- - '[nginx Configuration](/docs/websites/nginx/basic-nginx-configuration)'
+ - '[NGINX Configuration](/docs/websites/nginx/basic-nginx-configuration)'
---
-The nginx web server can act as a very capable software load balancer, in addition to its more traditional roles serving static content over HTTP and dynamic content using FastCGI handlers for scripts. Because ngnix uses a non-threaded, event-driven architecture, it is able to outperform web servers like Apache. This is particularly true in deployments that receive heavy loads.
+The NGINX web server can act as a very capable software load balancer, in addition to its more traditional roles serving static content over HTTP and dynamic content using FastCGI handlers for scripts. Because NGINX uses a non-threaded, event-driven architecture, it is able to outperform web servers like Apache. This is particularly true in deployments that receive heavy loads.
-
+
-Using a proxy is helpful when the demands of serving a single website outgrow the capabilities of a single machine. Additionally, there are some web frameworks, like [Seaside](/docs/frameworks/seaside/) and Ruby On Rails's Mongrel server, that deploy applications on framework-specific web servers. While these single-purpose servers provide powerful application services, they are not suitable for hosting entire applications. In these cases, using nginx as a front-end proxy to pass only the essential requests to the application server is a viable means of unifying dynamic content with static content and providing a stable production environment.
+Using a proxy is helpful when the demands of serving a single website outgrow the capabilities of a single machine. Additionally, there are some web frameworks, like [Seaside](/docs/frameworks/seaside/) and Ruby On Rails's Mongrel server, that deploy applications on framework-specific web servers. While these single-purpose servers provide powerful application services, they are not suitable for hosting entire applications. In these cases, using NGINX as a front-end proxy to pass only the essential requests to the application server is a viable means of unifying dynamic content with static content and providing a stable production environment.
-This document provides an overview of using nginx as a front-end proxy server for other HTTP servers, and as a software load balancer to distribute traffic across a cluster of machines providing HTTP resources. For an introductory guide to configuring nginx, please see our [Basic Nginx Configuration](/docs/websites/nginx/basic-nginx-configuration) guide. If you want a simple nginx deployment with content that uses PHP or Perl scripts, consider following one of our [Installing Nginx](/docs/web-servers/nginx/) guides.
+This document provides an overview of using NGINX as a front-end proxy server for other HTTP servers, and as a software load balancer to distribute traffic across a cluster of machines providing HTTP resources. For an introductory guide to configuring NGINX, please see our [Basic NGINX Configuration](/docs/websites/nginx/basic-nginx-configuration) guide. If you want a simple NGINX deployment with content that uses PHP or Perl scripts, consider following one of our [Installing NGINX](/docs/web-servers/nginx/) guides.
## Prerequisites
Before we begin, make sure you have completed the following:
- Follow the [Getting Started](/docs/getting-started/) guide.
-- Install the [nginx server](/docs/web-servers/nginx/).
-- Familiarize yourself with [Basic Nginx Configuration](/docs/websites/nginx/basic-nginx-configuration).
+- Install the [NGINX server](/docs/web-servers/nginx/).
+- Familiarize yourself with [Basic NGINX Configuration](/docs/websites/nginx/basic-nginx-configuration).
If you're new to Linux server administration, you may be interested in our [introduction to Linux basics](/docs/tools-reference/introduction-to-linux-concepts) guide, [Beginner's Guide](/docs/beginners-guide/) and [Administration Basics](/docs/using-linux/administration-basics) guide.
-## Front-End Proxy Services with Nginx: How It Works
+## Front-End Proxy Services with NGINX: How It Works
-When a request reaches the nginx front-end proxy server, here's an overview of the process that occurs:
+When a request reaches the NGINX front-end proxy server, here's an overview of the process that occurs:
-1. nginx receives a request for a resource.
-2. nginx sends a second *proxied* request to a specified server, and gets a response.
-3. nginx returns the result of that request to the original requester.
+1. NGINX receives a request for a resource.
+2. NGINX sends a second *proxied* request to a specified server, and gets a response.
+3. NGINX returns the result of that request to the original requester.
## Configure Apache for Port Listening
-In this section, you'll configure Apache to listen on an alternate port so it can respond to the nginx front end.
+In this section, you'll configure Apache to listen on an alternate port so it can respond to the NGINX front end.
{{< note >}}
This guide assumes you are using Apache 2.4. Some path names will be slightly different if you are using an older version.
{{< /note >}}
-1. The first thing you will configure is the port on which Apache listens. This needs to be a port other than 80, so that you can proxy requests to Apache on the alternate port. This has the added benefit of preventing conflicts between Apache and nginx listening on the same port. First, open up the `/etc/apache2/ports.conf` file for editing, and configure it as shown below:
+1. The first thing you will configure is the port on which Apache listens. This needs to be a port other than 80, so that you can proxy requests to Apache on the alternate port. This has the added benefit of preventing conflicts between Apache and NGINX listening on the same port. First, open up the `/etc/apache2/ports.conf` file for editing, and configure it as shown below:
sudo nano /etc/apache2/ports.conf
@@ -101,7 +101,7 @@ Listen 8000
{{< /file-excerpt >}}
-3. In the `/etc/apache2/apache2.conf` file, comment out the `LogFormat {User-Agent}` line. Then, add a forward so that Apache will log the original user’s IP address in the access logs instead of nginx's IP address (which would be listed as 127.0.0.1).
+3. In the `/etc/apache2/apache2.conf` file, comment out the `LogFormat {User-Agent}` line. Then, add a forward so that Apache will log the original user’s IP address in the access logs instead of NGINX's IP address (which would be listed as 127.0.0.1).
sudo nano /etc/apache2/apache2.conf
@@ -120,7 +120,7 @@ LogFormat "%{X-Forwarded-For}i %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-A
service apache restart
-6. Edit the `/etc/nginx/proxy_params` file. These settings are a good starting point for optimal forwarding of proxy requests from Nginx to Apache:
+6. Edit the `/etc/nginx/proxy_params` file. These settings are a good starting point for optimal forwarding of proxy requests from NGINX to Apache:
sudo nano /etc/nginx/proxy_params
@@ -143,7 +143,7 @@ proxy_read_timeout 300;
{{< /file >}}
-7. Create the nginx `example.com` virtual host file at `/etc/nginx/sites-available/example.com`. Make sure you specify the same document root here that you did for Apache (for example, `/var/www/html/example.com`). This will ensure that nginx can deliver static files directly without passing the request to Apache. Static files (like JavaScript, CSS, images, PDF files, static HTML files, etc.) can be delivered much faster with nginx than Apache.
+7. Create the NGINX `example.com` virtual host file at `/etc/nginx/sites-available/example.com`. Make sure you specify the same document root here that you did for Apache (for example, `/var/www/html/example.com`). This will ensure that NGINX can deliver static files directly without passing the request to Apache. Static files (like JavaScript, CSS, images, PDF files, static HTML files, etc.) can be delivered much faster with NGINX than Apache.
sudo nano /etc/nginx/sites-available/example.com
@@ -174,7 +174,7 @@ server {
There are some additional `location` directives to add in the `server` section of the `/etc/nginx/sites-available/example.com` file. You will probably need these directives, but it's possible that you may not, depending on your nginx and Apache configuration.
-8. Add a `location` directive to make nginx refuse all requests for files beginning with the characters `.ht`. There's a similar directive in nearly every default Apache configuration. This directive is useful if your Apache deployment relies on settings from `.htaccess` and `.htpasswd`.
+8. Add a `location` directive to make NGINX refuse all requests for files beginning with the characters `.ht`. There's a similar directive in nearly every default Apache configuration. This directive is useful if your Apache deployment relies on settings from `.htaccess` and `.htpasswd`.
{{< file-excerpt "/etc/nginx/sites-available/example.com" nginx >}}
location ~ /\.ht {
@@ -205,7 +205,7 @@ location / {
**Response:** `http://192.168.3.105/teams/~example/wiki/PracticeSchedule/`
-10. For most conventional proxy setups, you will also want to add a `proxy_redirect` specification to your `location` directive blocks. This directive rewrites the HTTP headers that nginx receives from the proxy server to make them appear as if they were generated by the nginx server.
+10. For most conventional proxy setups, you will also want to add a `proxy_redirect` specification to your `location` directive blocks. This directive rewrites the HTTP headers that NGINX receives from the proxy server to make them appear as if they were generated by the NGINX server.
{{< file-excerpt "example.com.vhost proxy location directive" nginx >}}
location /pictures/ {
@@ -220,7 +220,7 @@ location /pictures/ {
## Software Load Balancing
-In addition to using nginx as a front-end proxy to pass requests to other web servers, nginx can also serve as the front end for clusters of servers, and even as a software load balancer.
+In addition to using NGINX as a front-end proxy to pass requests to other web servers, NGINX can also serve as the front end for clusters of servers, and even as a software load balancer.
### Basic HTTP Clustering
@@ -255,7 +255,7 @@ upstream appcluster {
{{< /file-excerpt >}}
-In this example, in the `server` directive block, nginx is configured to listen for requests on a specific IP address and port (e.g. `192.0.2.0` and `80`), and respond to requests for the domains `example.com` and `www.example.com`. All requests for resources at this domain (e.g. `/`) will be passed to the `http://appcluster` server established in the `upstream` directive.
+In this example, in the `server` directive block, NGINX is configured to listen for requests on a specific IP address and port (e.g. `192.0.2.0` and `80`), and respond to requests for the domains `example.com` and `www.example.com`. All requests for resources at this domain (e.g. `/`) will be passed to the `http://appcluster` server established in the `upstream` directive.
The `upstream` directive establishes the round-robin load balancer. Within this block eight servers are listed, each running on a distinct hostname and port combination.
@@ -265,7 +265,7 @@ The `upstream` directive establishes the round-robin load balancer. Within this
### Advanced Load Balancing
-nginx also allows you to control the behavior of the `upstream` resource cluster beyond a simple round-robin setup. The simplest modification is to add the `ip_hash` directive to the configuration block. This causes requests from the same IP address to be routed to the same back-end server. Consider the following example excerpt:
+NGINX also allows you to control the behavior of the `upstream` resource cluster beyond a simple round-robin setup. The simplest modification is to add the `ip_hash` directive to the configuration block. This causes requests from the same IP address to be routed to the same back-end server. Consider the following example excerpt:
{{< file-excerpt "/etc/nginx/sites-available/example.com" nginx >}}
upstream appcluster {
@@ -279,7 +279,7 @@ upstream appcluster {
{{< /file-excerpt >}}
-Here, the `ip_hash` directive causes nginx to attempt to match requests originating from a single IP address with the same back-end component. If a component server is unreachable, nginx will route those connections to an alternate component.
+Here, the `ip_hash` directive causes NGINX to attempt to match requests originating from a single IP address with the same back-end component. If a component server is unreachable, NGINX will route those connections to an alternate component.
{{< note >}}
If a server needs to be taken offline for an extended period of time, append the `down` argument, as shown in the entry for `galloway.example.com:8801`. This will prevent missed connections from attempting to hit a component of the server which is down.
@@ -301,11 +301,11 @@ upstream appcluster {
{{< /file-excerpt >}}
-Using these arguments, you can use nginx to manage the behavior and distribution of load across a cluster of servers:
+Using these arguments, you can use NGINX to manage the behavior and distribution of load across a cluster of servers:
- By default, each server listed in an upstream cluster has a weight of `1`. The argument `weight=[number]` sets a specific weight. Higher numbers receive more weight.
- In the example above, the components running on ports `8801` and `8802` are treated identically by nginx, as the default value for `weight` is `1`. The components running on `8803`, `8804`, and `8807` will receive twice as much traffic as the first two components. The components running on `8805` and `8806` will receive four times as much traffic as the ones on `8801` and `8802` and twice much traffic as the components on `8803`, `8804`, and `8807`.
+ In the example above, the components running on ports `8801` and `8802` are treated identically by NGINX, as the default value for `weight` is `1`. The components running on `8803`, `8804`, and `8807` will receive twice as much traffic as the first two components. The components running on `8805` and `8806` will receive four times as much traffic as the ones on `8801` and `8802` and twice much traffic as the components on `8803`, `8804`, and `8807`.
- `max_fails=[number]` specifies the number of unsuccessful attempts at communication with an upstream component before it is considered inoperative. To prevent components from ever being marked as inoperative, even if they are unreachable, set this value to `0`. The default value for `max_fails` is `1`.
diff --git a/docs/uptime/monitoring/monitor-systems-logwatch.md b/docs/uptime/monitoring/monitor-systems-logwatch.md
index ee4e0dbe4cd..c014a7cadf4 100644
--- a/docs/uptime/monitoring/monitor-systems-logwatch.md
+++ b/docs/uptime/monitoring/monitor-systems-logwatch.md
@@ -146,12 +146,12 @@ The default Logwatch configuration will output the digest to your Linode's conso
The Logwatch digest can be sent to local users or external email addresses, in plain text or HTML formats.
{{< note >}}
-Prior to sending mail externally or locally ensure you have Sendmail installed on the Linode. If you choose to use a different MTA client, change the `mailer` line in the Logwatch configuration file to contain the directory of your choosen MTA, or alias `/usr/sbin/sendmail` to your MTA.
+Prior to sending mail externally or locally ensure you have Sendmail installed on the Linode. If you choose to use a different MTA client, change the `mailer` line in the Logwatch configuration file to contain the directory of your chosen MTA, or alias `/usr/sbin/sendmail` to your MTA.
If using Arch, and you followed the above install instructions, Sendmail is already aliased to msmtp.
{{< /note >}}
-1. Change the `Output` value to `mail`. If you wish to recieve the messages in HTML format change the `Format` value to `html`.
+1. Change the `Output` value to `mail`. If you wish to receive the messages in HTML format change the `Format` value to `html`.
2. Change the `MailTo` address to a valid email address, or local account user. For example, to send mail to the `root` user change the line to read:
diff --git a/docs/uptime/monitoring/ossec-ids-debian-7.md b/docs/uptime/monitoring/ossec-ids-debian-7.md
index 891ad139835..1cbbabd9f77 100644
--- a/docs/uptime/monitoring/ossec-ids-debian-7.md
+++ b/docs/uptime/monitoring/ossec-ids-debian-7.md
@@ -15,7 +15,7 @@ modified_by:
published: 2015-02-05
title: Install and Configure OSSEC on Debian 7
external_resources:
- - '[http://www.ossec.net/](http://www.ossec.net)'
+ - '[OSSEC](https://ossec.github.io/)'
---
@@ -23,7 +23,7 @@ OSSEC is an open-source, host-based intrusion detection system (**HIDS**) that p
When installed and configured, OSSEC will provide a real-time view of what's taking place in your server or servers in a server/agent mode.
-This guide covers how to install and configure OSSEC on a single Linode running Debian 7 in such a manner that if a file is modified, added or deleted, OSSEC will notify you by email in real-time. OSSEC can also provide notifications for other acitivies.
+This guide covers how to install and configure OSSEC on a single Linode running Debian 7 in such a manner that if a file is modified, added or deleted, OSSEC will notify you by email in real-time. OSSEC can also provide notifications for other activities.
{{< note >}}
This guide is written for a non-root user. Commands that require elevated privileges are prefixed with `sudo`. If you're not familiar with the `sudo` command, you can check our [Users and Groups](/docs/tools-reference/linux-users-and-groups) guide.
diff --git a/docs/web-servers/apache/how-to-set-up-htaccess-on-apache.md b/docs/web-servers/apache/how-to-set-up-htaccess-on-apache.md
index abc29b88911..bf6ed59e0a1 100644
--- a/docs/web-servers/apache/how-to-set-up-htaccess-on-apache.md
+++ b/docs/web-servers/apache/how-to-set-up-htaccess-on-apache.md
@@ -174,7 +174,7 @@ The next parameter is the Unix path to the file that is requested in the URL. Th
### Set the 404 Error Page
-When a visitor attempts to access a page or resource that doesn't exist (for example by following a broken link or typing an incorrect URL,) the server will respond with a 404 error code. It is important that users receive feedback explaning the error. By default, Apache will display an error page in the event of a 404 error. However, most sites provide a customized error page. You can use .htaccess settings to let Apache know what error page you would like displayed whenever a user attempts to access a nonexistent page.
+When a visitor attempts to access a page or resource that doesn't exist (for example by following a broken link or typing an incorrect URL,) the server will respond with a 404 error code. It is important that users receive feedback explaining the error. By default, Apache will display an error page in the event of a 404 error. However, most sites provide a customized error page. You can use .htaccess settings to let Apache know what error page you would like displayed whenever a user attempts to access a nonexistent page.
1. This will redirect all requests for nonexistent documents to a page in the project root directory called `404.html. Open the .htaccess file and add the following line:
diff --git a/docs/web-servers/apache/run-php-cgi-apache-centos-6.md b/docs/web-servers/apache/run-php-cgi-apache-centos-6.md
index d8eb4a254d3..0e579bd7826 100644
--- a/docs/web-servers/apache/run-php-cgi-apache-centos-6.md
+++ b/docs/web-servers/apache/run-php-cgi-apache-centos-6.md
@@ -17,7 +17,7 @@ external_resources:
- '[Apache 2.2 CGI documentation](http://httpd.apache.org/docs/2.2/howto/cgi.html)'
---
-In instances where running the `mod_php` module to run PHP scripts on Apache is not sufficient, PHP can be run as a CGI binary. Combined with the `itk` multi-processing module (MPM), PHP scripts can be run as user processes in a per-virtual host setup. This guide will walk users through the proccess of setting up Apache and PHP CGI.
+In instances where running the `mod_php` module to run PHP scripts on Apache is not sufficient, PHP can be run as a CGI binary. Combined with the `itk` multi-processing module (MPM), PHP scripts can be run as user processes in a per-virtual host setup. This guide will walk users through the process of setting up Apache and PHP CGI.
{{< note >}}
This guide is written for a non-root user. Commands that require elevated privileges are prefixed with `sudo`. If you're not familiar with the `sudo` command, you can check our [Users and Groups](/docs/tools-reference/linux-users-and-groups) guide.
@@ -30,7 +30,7 @@ This guide is written for a non-root user. Commands that require elevated privil
To check your hostname run:
hostname
- hostname -f
+ hostname -f
The first command should show your short hostname, and the second should show your fully qualified domain name (FQDN).
diff --git a/docs/web-servers/apache/run-php-cgi-apache-ubuntu-12-04.md b/docs/web-servers/apache/run-php-cgi-apache-ubuntu-12-04.md
index 0d5941d5355..e19dce904ef 100644
--- a/docs/web-servers/apache/run-php-cgi-apache-ubuntu-12-04.md
+++ b/docs/web-servers/apache/run-php-cgi-apache-ubuntu-12-04.md
@@ -17,7 +17,7 @@ external_resources:
- '[Apache 2.2 CGI documentation](http://httpd.apache.org/docs/2.2/howto/cgi.html)'
---
-In instances where running the `mod_php` module to run PHP scripts on Apache is not sufficient, PHP can be run as a CGI binary. Combined with the `itk` multi-processing module (MPM), PHP scripts can be run as user processes in a per-virtual host setup. This guide will walk users through the proccess of setting up Apache and PHP CGI.
+In instances where running the `mod_php` module to run PHP scripts on Apache is not sufficient, PHP can be run as a CGI binary. Combined with the `itk` multi-processing module (MPM), PHP scripts can be run as user processes in a per-virtual host setup. This guide will walk users through the process of setting up Apache and PHP CGI.
{{< note >}}
This guide is written for a non-root user. Commands that require elevated privileges are prefixed with `sudo`. If you're not familiar with the `sudo` command, you can check our [Users and Groups](/docs/tools-reference/linux-users-and-groups) guide.
@@ -30,7 +30,7 @@ This guide is written for a non-root user. Commands that require elevated privil
To check your hostname, run:
hostname
- hostname -f
+ hostname -f
The first command should show your short hostname, and the second should show your fully qualified domain name (FQDN).
@@ -108,7 +108,7 @@ This may not be ideal if you have multiple users running publicly accessible scr
{{< file-excerpt "Apache Virtual Hosting Configuration Block" apache >}}
- AssignUserId webeditor webgroup
+ AssignUserId webeditor webgroup
{{< /file-excerpt >}}
diff --git a/docs/web-servers/apache/run-php-cgi-apapache-debian-7.md b/docs/web-servers/apache/run-php-cgi-apapache-debian-7.md
index 02e352e853b..f02041ea8d4 100644
--- a/docs/web-servers/apache/run-php-cgi-apapache-debian-7.md
+++ b/docs/web-servers/apache/run-php-cgi-apapache-debian-7.md
@@ -17,7 +17,7 @@ external_resources:
- '[Apache 2.2 CGI documentation](http://httpd.apache.org/docs/2.2/howto/cgi.html)'
---
-In instances where running the `mod_php` module to run PHP scripts on Apache is not sufficient, PHP can be run as a CGI binary. Combined with the `itk` multi-processing module (MPM), PHP scripts can be run as user processes in a per-virtual host setup. This guide will walk users through the proccess of setting up Apache and PHP CGI.
+In instances where running the `mod_php` module to run PHP scripts on Apache is not sufficient, PHP can be run as a CGI binary. Combined with the `itk` multi-processing module (MPM), PHP scripts can be run as user processes in a per-virtual host setup. This guide will walk users through the process of setting up Apache and PHP CGI.
{{< note >}}
This guide is written for a non-root user. Commands that require elevated privileges are prefixed with `sudo`. If you're not familiar with the `sudo` command, you can check our [Users and Groups](/docs/tools-reference/linux-users-and-groups) guide.
diff --git a/docs/web-servers/cherokee/web-apps-with-cherokee-and-phpfastcgi-on-fedora-13.md b/docs/web-servers/cherokee/web-apps-with-cherokee-and-phpfastcgi-on-fedora-13.md
index 6acd4ea99da..9c79fad8828 100644
--- a/docs/web-servers/cherokee/web-apps-with-cherokee-and-phpfastcgi-on-fedora-13.md
+++ b/docs/web-servers/cherokee/web-apps-with-cherokee-and-phpfastcgi-on-fedora-13.md
@@ -135,7 +135,7 @@ Create a test PHP script as follows:
{{< /file >}}
-Visit `/test.php` on your site to verfify PHP-FastCGI is operating correctly. Congratulations, you've successfully configured PHP-FastCGI for dynamic content using the Cherokee web server!
+Visit `/test.php` on your site to verify PHP-FastCGI is operating correctly. Congratulations, you've successfully configured PHP-FastCGI for dynamic content using the Cherokee web server!
# More Information
diff --git a/docs/web-servers/cherokee/web-apps-with-cherokee-and-phpfastcgi-on-ubuntu-10-04-lts-lucid.md b/docs/web-servers/cherokee/web-apps-with-cherokee-and-phpfastcgi-on-ubuntu-10-04-lts-lucid.md
index 4a106c0d8a1..87bd57e02c0 100644
--- a/docs/web-servers/cherokee/web-apps-with-cherokee-and-phpfastcgi-on-ubuntu-10-04-lts-lucid.md
+++ b/docs/web-servers/cherokee/web-apps-with-cherokee-and-phpfastcgi-on-ubuntu-10-04-lts-lucid.md
@@ -117,7 +117,7 @@ Restart Cherokee by clicking the "Save" button under the left page navigation li
{{< /file >}}
-Visit "/test.php" on your site to verfify PHP-FastCGI is operating correctly. You should see the standard PHPInfo page. Congratulations, you've successfully configured PHP-FastCGI for dynamic content using the Cherokee web server!
+Visit "/test.php" on your site to verify PHP-FastCGI is operating correctly. You should see the standard PHPInfo page. Congratulations, you've successfully configured PHP-FastCGI for dynamic content using the Cherokee web server!
# More Information
diff --git a/docs/web-servers/lamp/lamp-server-on-debian-7-wheezy.md b/docs/web-servers/lamp/lamp-server-on-debian-7-wheezy.md
index 88f10530055..49edbbd78af 100644
--- a/docs/web-servers/lamp/lamp-server-on-debian-7-wheezy.md
+++ b/docs/web-servers/lamp/lamp-server-on-debian-7-wheezy.md
@@ -132,7 +132,7 @@ Assuming that you have configured the DNS for your domain to point to your Linod
Enter the root password. The MySQL prompt will appear.
-2. Create a database and a user with permissions for it. In this example the databse is called `webdata`, the user `webuser` and password `password`:
+2. Create a database and a user with permissions for it. In this example the database is called `webdata`, the user `webuser` and password `password`:
create database webdata;
grant all on webdata.* to 'webuser' identified by 'password';
diff --git a/docs/web-servers/lemp/how-to-install-a-lemp-server-on-ubuntu-16-04.md b/docs/web-servers/lemp/how-to-install-a-lemp-server-on-ubuntu-16-04.md
index 46715ff53db..6b0d28a3201 100644
--- a/docs/web-servers/lemp/how-to-install-a-lemp-server-on-ubuntu-16-04.md
+++ b/docs/web-servers/lemp/how-to-install-a-lemp-server-on-ubuntu-16-04.md
@@ -28,7 +28,7 @@ This guide describes an alternative to the *LAMP* (Linux, Apache, MySQL, and PHP
- Update your system:
- sudo apt-get update && sudo apt-get upgrade
+ sudo apt-get update && sudo apt-get upgrade
{{< note >}}
This guide is written for a non-root user. Commands that require elevated privileges are prefixed with `sudo`. If you’re not familiar with the `sudo` command, see the [Linux Users and Groups Guide](/docs/tools-reference/linux-users-and-groups).
@@ -84,7 +84,7 @@ index index.html index.php;
{{< /file-excerpt >}}
-3. The nginx example configuration uses `/var/www/` as a document root, but Ubuntu uses `/var/www/html` as a standard. Additionally, Linode guides encourage the standard practice of using a subdirectory called `public_html` to exclude web files that shouldn't be publicly accesible. Update the `root` directive to match these conventions:
+3. The nginx example configuration uses `/var/www/` as a document root, but Ubuntu uses `/var/www/html` as a standard. Additionally, Linode guides encourage the standard practice of using a subdirectory called `public_html` to exclude web files that shouldn't be publicly accessible. Update the `root` directive to match these conventions:
{{< file-excerpt "/etc/nginx/sites-available/example.com" nginx >}}
root /var/www/html/example.com/public_html;
diff --git a/docs/web-servers/lighttpd/lighttpd-web-server-on-debian-5-lenny.md b/docs/web-servers/lighttpd/lighttpd-web-server-on-debian-5-lenny.md
index dac718d79a1..1d8ee635eea 100644
--- a/docs/web-servers/lighttpd/lighttpd-web-server-on-debian-5-lenny.md
+++ b/docs/web-servers/lighttpd/lighttpd-web-server-on-debian-5-lenny.md
@@ -154,7 +154,7 @@ No matter what you decide, we recommend developing some sort of systematic metho
# Running Scripts with mod\_fastcgi
-If you need your web server to execute dynamic content, the preferred way to accomplish this with lighttpd is to run these scripts using FastCGI. To run a script, FastCGI externalizes the interpreter for the script for dynamic web applications from the web server rather than running the scripts "inside" the web server. This is in contrast to the common Apache-based approaches such as mod\_perl, mod\_python, and mod\_php. If you're familar with Apache this might seem foreign and/or antiquated, but in high-traffic situations doing things this way is often more efficient and effective.
+If you need your web server to execute dynamic content, the preferred way to accomplish this with lighttpd is to run these scripts using FastCGI. To run a script, FastCGI externalizes the interpreter for the script for dynamic web applications from the web server rather than running the scripts "inside" the web server. This is in contrast to the common Apache-based approaches such as mod_perl, mod_python, and mod_php. If you're familiar with Apache this might seem foreign and/or antiquated, but in high-traffic situations doing things this way is often more efficient and effective.
To set up FastCGI you need to make sure that an interpreter is installed on your system that is capable of running your scripts. Perl version 5.10.0-19 is installed in Debian Lenny by default. Issue one of the following commands:
diff --git a/docs/web-servers/lighttpd/lighttpd-web-server-on-ubuntu-12-04-preci.md b/docs/web-servers/lighttpd/lighttpd-web-server-on-ubuntu-12-04-preci.md
index 4aeb8005e53..29ea952e7e7 100644
--- a/docs/web-servers/lighttpd/lighttpd-web-server-on-ubuntu-12-04-preci.md
+++ b/docs/web-servers/lighttpd/lighttpd-web-server-on-ubuntu-12-04-preci.md
@@ -188,7 +188,7 @@ No matter what you decide, we recommend developing some sort of systematic metho
## Running Scripts with mod\_fastcgi
-If you need your web server to execute dynamic content, the preferred way to accomplish this with lighttpd is to run these scripts using FastCGI. To run a script, FastCGI externalizes the interpreter for the script for dynamic web applications from the web server rather than running the scripts "inside" the web server. This is in contrast to the common Apache-based approaches such as mod\_perl, mod\_python, and mod\_php. If you're familar with Apache this might seem foreign and/or antiquated, but in high-traffic situations doing things this way is often more efficient and effective.
+If you need your web server to execute dynamic content, the preferred way to accomplish this with lighttpd is to run these scripts using FastCGI. To run a script, FastCGI externalizes the interpreter for the script for dynamic web applications from the web server rather than running the scripts "inside" the web server. This is in contrast to the common Apache-based approaches such as mod_perl, mod_python, and mod_php. If you're familiar with Apache this might seem foreign and/or antiquated, but in high-traffic situations doing things this way is often more efficient and effective.
To set up FastCGI you need to make sure that an interpreter is installed on your system that is capable of running your scripts. Perl version 5.14.2 is included in Ubuntu by default. Issue one of the following commands:
diff --git a/docs/web-servers/lighttpd/lighttpd-web-server-on-ubuntu-9-10-karmic.md b/docs/web-servers/lighttpd/lighttpd-web-server-on-ubuntu-9-10-karmic.md
index 588538e051c..c067dcde003 100644
--- a/docs/web-servers/lighttpd/lighttpd-web-server-on-ubuntu-9-10-karmic.md
+++ b/docs/web-servers/lighttpd/lighttpd-web-server-on-ubuntu-9-10-karmic.md
@@ -207,7 +207,7 @@ No matter what you decide, we recommend developing some sort of systematic metho
# Running Scripts with mod\_fastcgi
-If you need your web server to execute dynamic content, the preferred way to accomplish this with lighttpd is to run these scripts using FastCGI. To run a script, FastCGI externalizes the interpreter for the script for dynamic web applications from the web server rather than running the scripts "inside" the web server. This is in contrast to the common Apache-based approaches such as mod\_perl, mod\_python, and mod\_php. If you're familar with Apache this might seem foreign and/or antiquated, but in high-traffic situations doing things this way is often more efficient and effective.
+If you need your web server to execute dynamic content, the preferred way to accomplish this with lighttpd is to run these scripts using FastCGI. To run a script, FastCGI externalizes the interpreter for the script for dynamic web applications from the web server rather than running the scripts "inside" the web server. This is in contrast to the common Apache-based approaches such as mod_perl, mod_python, and mod_php. If you're familiar with Apache this might seem foreign and/or antiquated, but in high-traffic situations doing things this way is often more efficient and effective.
To set up FastCGI you need to make sure that an interpreter is installed on your system that is capable of running your scripts. Perl version 5.10.0-19 is included in Ubuntu by default. Issue one of the following commands:
diff --git a/docs/web-servers/nginx/install-nginx-and-a-startssl-certificate-on-debian-7-wheezy.md b/docs/web-servers/nginx/install-nginx-and-a-startssl-certificate-on-debian-7-wheezy.md
index 88f0cc8d7a3..4289f5153cc 100644
--- a/docs/web-servers/nginx/install-nginx-and-a-startssl-certificate-on-debian-7-wheezy.md
+++ b/docs/web-servers/nginx/install-nginx-and-a-startssl-certificate-on-debian-7-wheezy.md
@@ -71,7 +71,7 @@ All of the commands below should be executed as the ``root`` user.
cd /etc/ssl/nginx
-3. Generate a 2048 bit RSA private key. If you are paranoid you could change 2048 to 4096 to create a 4096 bit private key. Currently, most certificate authorities are requring customers to use a 2048 bit or higher RSA private key.
+3. Generate a 2048 bit RSA private key. If you are paranoid you could change 2048 to 4096 to create a 4096 bit private key. Currently, most certificate authorities are requiring customers to use a 2048 bit or higher RSA private key.
openssl genrsa -out server.key 2048
@@ -83,7 +83,7 @@ All of the commands below should be executed as the ``root`` user.
### Sign-up With StartSSL
-1. Launch a web browser and naviagte to the [StartSSL Control Panel](https://www.startssl.com/?app=12). If this is your first time requesting a certificate from StartSSL, click on the "Sign-up" button. If you have already requested a certificate from StartSSL, log into your account, and skip to the next section.
+1. Launch a web browser and navigate to the [StartSSL Control Panel](https://www.startssl.com/?app=12). If this is your first time requesting a certificate from StartSSL, click on the "Sign-up" button. If you have already requested a certificate from StartSSL, log into your account, and skip to the next section.
[](/docs/assets/1752-StartSSL-Control-Panel.jpg)
@@ -133,7 +133,7 @@ You should now be logged into your StartSSL account.
1. Click on the "Certificates Wizard" button in your StartSSL account.
-2. From the "Certificate Target" drop down menu select "Web Server SSL/TLS Certicate" and click "Continue >> >>".
+2. From the "Certificate Target" drop down menu select "Web Server SSL/TLS Certificate" and click "Continue >> >>".
[](/docs/assets/1761-StartSSL-Certificates-Wizard-Target.jpg)
diff --git a/docs/web-servers/nginx/install-nginx-and-a-startssl-certificate-on-debian-8-jessie.md b/docs/web-servers/nginx/install-nginx-and-a-startssl-certificate-on-debian-8-jessie.md
index 4bbb5502752..68db457e824 100644
--- a/docs/web-servers/nginx/install-nginx-and-a-startssl-certificate-on-debian-8-jessie.md
+++ b/docs/web-servers/nginx/install-nginx-and-a-startssl-certificate-on-debian-8-jessie.md
@@ -195,7 +195,7 @@ You should now be logged into your StartSSL account.
1. Click on the "Certificates Wizard" button in your StartSSL account.
-2. Select "Web Server SSL/TLS Certicate" and click **Continue**.
+2. Select "Web Server SSL/TLS Certificate" and click **Continue**.
[](/docs/assets/startssl-certificate1.png)
diff --git a/docs/web-servers/nginx/install-nginx-and-php-via-fastcgi-on-ubuntu-12-04-precise-pangolin.md b/docs/web-servers/nginx/install-nginx-and-php-via-fastcgi-on-ubuntu-12-04-precise-pangolin.md
index 11ee55f7c82..47c6cd7cd5a 100644
--- a/docs/web-servers/nginx/install-nginx-and-php-via-fastcgi-on-ubuntu-12-04-precise-pangolin.md
+++ b/docs/web-servers/nginx/install-nginx-and-php-via-fastcgi-on-ubuntu-12-04-precise-pangolin.md
@@ -270,7 +270,7 @@ When you visit `http://www.example.com/test.php` in your browser, the standard "
You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
-- [The nginx Homepage](http://nginx.org/)
+- [The NGINX Homepage](http://nginx.org/)
- [FastCGI Project Homepage](http://www.fastcgi.com/)
- [PHP Documentation](http://www.php.net/docs.php)
-- [Basic Ngnix Configuration](/docs/websites/nginx/basic-nginx-configuration)
+- [Basic NGINX Configuration](/docs/websites/nginx/basic-nginx-configuration)
diff --git a/docs/web-servers/nginx/installing-nginx-on-ubuntu-12-04-lts-precise-pangolin.md b/docs/web-servers/nginx/installing-nginx-on-ubuntu-12-04-lts-precise-pangolin.md
index 8dad5e152e9..74d0de5f0bd 100644
--- a/docs/web-servers/nginx/installing-nginx-on-ubuntu-12-04-lts-precise-pangolin.md
+++ b/docs/web-servers/nginx/installing-nginx-on-ubuntu-12-04-lts-precise-pangolin.md
@@ -61,7 +61,7 @@ This method is the easiest and it ensures that Nginx has been tested to run at i
Nginx's [downloads page](https://www.nginx.com/download-oss-information/) has two more ways to install the web server: Using pre-built packages from the official Nginx repository or by building from source code. Either method will give you a more current version than what's available in Trusty Tahr but with a slightly higher chance of encountering unforseen issues because of newly-introduced bugs, and that these releases are not tested exclusively for a specific Linux distribution.
-#### Installing from the Offcial Nginx Repository
+#### Installing from the Official Nginx Repository
The binary packages from Nginx's repo will update you to new versions of the web server when available. You can choose the [stable](http://nginx.org/en/linux_packages.html#stable) or [mainline](http://nginx.org/en/linux_packages.html#mainline) versions. If unsure, choose stable, which will be the example used for the remainder of this guide.
diff --git a/docs/web-servers/nginx/nginx-and-perlfastcgi-on-debian-5-lenny.md b/docs/web-servers/nginx/nginx-and-perlfastcgi-on-debian-5-lenny.md
index 4208498e0d6..6e00d0eb17d 100644
--- a/docs/web-servers/nginx/nginx-and-perlfastcgi-on-debian-5-lenny.md
+++ b/docs/web-servers/nginx/nginx-and-perlfastcgi-on-debian-5-lenny.md
@@ -127,8 +127,8 @@ When you visit `http://www.example.com/test.pl` in your browser, your Perl envir
You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
-- [The nginx Homepage](http://nginx.org/)
+- [The NGINX Homepage](http://nginx.org/)
- [FastCGI Project Homepage](http://www.fastcgi.com/)
- [Perl Documentation](http://perldoc.perl.org/)
-- [Installing Nginx on Debian 5 (Lenny)](/docs/web-servers/nginx/installation/debian-5-lenny)
-- [Basic Ngnix Configuration](/docs/websites/nginx/basic-nginx-configuration)
+- [Installing NGINX on Debian 5 (Lenny)](/docs/web-servers/nginx/installation/debian-5-lenny)
+- [Basic NGINX Configuration](/docs/websites/nginx/basic-nginx-configuration)
diff --git a/docs/web-servers/nginx/nginx-and-perlfastcgi-on-debian-6-squeeze.md b/docs/web-servers/nginx/nginx-and-perlfastcgi-on-debian-6-squeeze.md
index cdd5f85fea1..a1ab2dc7221 100644
--- a/docs/web-servers/nginx/nginx-and-perlfastcgi-on-debian-6-squeeze.md
+++ b/docs/web-servers/nginx/nginx-and-perlfastcgi-on-debian-6-squeeze.md
@@ -174,7 +174,7 @@ When you visit `http://www.example.com/test.pl` in your browser, your Perl envir
You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
-- [The nginx Homepage](http://nginx.org/)
+- [The NGINX Homepage](http://nginx.org/)
- [FastCGI Project Homepage](http://www.fastcgi.com/)
- [Perl Documentation](http://perldoc.perl.org/)
-- [Basic Ngnix Configuration](/docs/websites/nginx/basic-nginx-configuration)
+- [Basic NGINX Configuration](/docs/websites/nginx/basic-nginx-configuration)
diff --git a/docs/web-servers/nginx/nginx-and-perlfastcgi-on-fedora-12.md b/docs/web-servers/nginx/nginx-and-perlfastcgi-on-fedora-12.md
index c49f6156b27..73ec089e2e0 100644
--- a/docs/web-servers/nginx/nginx-and-perlfastcgi-on-fedora-12.md
+++ b/docs/web-servers/nginx/nginx-and-perlfastcgi-on-fedora-12.md
@@ -150,8 +150,8 @@ When you visit `http://www.example.com/test.pl` in your browser, your Perl envir
You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
-- [The nginx Homepage](http://nginx.org/)
+- [The NGINX Homepage](http://nginx.org/)
- [FastCGI Project Homepage](http://www.fastcgi.com/)
- [Perl Documentation](http://perldoc.perl.org/)
-- [Installing Nginx on Fedora 12](/docs/web-servers/nginx/installation/fedora-12)
-- [Basic Ngnix Configuration](/docs/websites/nginx/basic-nginx-configuration)
+- [Installing NGINX on Fedora 12](/docs/web-servers/nginx/installation/fedora-12)
+- [Basic NGINX Configuration](/docs/websites/nginx/basic-nginx-configuration)
diff --git a/docs/web-servers/nginx/nginx-and-perlfastcgi-on-fedora-13.md b/docs/web-servers/nginx/nginx-and-perlfastcgi-on-fedora-13.md
index 5034d3b314b..4ec77d6d9bd 100644
--- a/docs/web-servers/nginx/nginx-and-perlfastcgi-on-fedora-13.md
+++ b/docs/web-servers/nginx/nginx-and-perlfastcgi-on-fedora-13.md
@@ -148,8 +148,8 @@ When you visit `http://www.example.com/test.pl` in your browser, your Perl envir
You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
-- [The nginx Homepage](http://nginx.org/)
+- [The NGINX Homepage](http://nginx.org/)
- [FastCGI Project Homepage](http://www.fastcgi.com/)
- [Perl Documentation](http://perldoc.perl.org/)
-- [Installing Nginx on Fedora 13](/docs/web-servers/nginx/installation/fedora-13)
-- [Basic Ngnix Configuration](/docs/websites/nginx/basic-nginx-configuration)
+- [Installing NGINX on Fedora 13](/docs/web-servers/nginx/installation/fedora-13)
+- [Basic NGINX Configuration](/docs/websites/nginx/basic-nginx-configuration)
diff --git a/docs/web-servers/nginx/nginx-and-perlfastcgi-on-fedora-14.md b/docs/web-servers/nginx/nginx-and-perlfastcgi-on-fedora-14.md
index e0b5222421d..f1aff20b4ee 100644
--- a/docs/web-servers/nginx/nginx-and-perlfastcgi-on-fedora-14.md
+++ b/docs/web-servers/nginx/nginx-and-perlfastcgi-on-fedora-14.md
@@ -345,8 +345,8 @@ When you visit `http://www.example.com/test.pl` in your browser, your Perl envir
You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
-- [The nginx Homepage](http://nginx.org/)
+- [The NGINX Homepage](http://nginx.org/)
- [FastCGI Project Homepage](http://www.fastcgi.com/)
- [Perl Documentation](http://perldoc.perl.org/)
-- [Installing Nginx on Fedora 14](/docs/web-servers/nginx/installation/fedora-14)
-- [Basic Ngnix Configuration](/docs/websites/nginx/basic-nginx-configuration)
+- [Installing NGINX on Fedora 14](/docs/web-servers/nginx/installation/fedora-14)
+- [Basic NGINX Configuration](/docs/websites/nginx/basic-nginx-configuration)
diff --git a/docs/web-servers/nginx/nginx-and-perlfastcgi-on-ubuntu-10-04-lts-lucid.md b/docs/web-servers/nginx/nginx-and-perlfastcgi-on-ubuntu-10-04-lts-lucid.md
index d4125598b38..f7d0eddd0a7 100644
--- a/docs/web-servers/nginx/nginx-and-perlfastcgi-on-ubuntu-10-04-lts-lucid.md
+++ b/docs/web-servers/nginx/nginx-and-perlfastcgi-on-ubuntu-10-04-lts-lucid.md
@@ -194,7 +194,7 @@ When you visit `http://www.example.com/test.pl` in your browser, your Perl envir
You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
-- [The nginx Homepage](http://nginx.org/)
+- [The NGINX Homepage](http://nginx.org/)
- [FastCGI Project Homepage](http://www.fastcgi.com/)
- [Perl Documentation](http://perldoc.perl.org/)
-- [Basic Ngnix Configuration](/docs/websites/nginx/basic-nginx-configuration)
+- [Basic NGINX Configuration](/docs/websites/nginx/basic-nginx-configuration)
diff --git a/docs/web-servers/nginx/nginx-and-perlfastcgi-on-ubuntu-10-10-maverick.md b/docs/web-servers/nginx/nginx-and-perlfastcgi-on-ubuntu-10-10-maverick.md
index ce22978d92c..5e54b992d57 100644
--- a/docs/web-servers/nginx/nginx-and-perlfastcgi-on-ubuntu-10-10-maverick.md
+++ b/docs/web-servers/nginx/nginx-and-perlfastcgi-on-ubuntu-10-10-maverick.md
@@ -176,7 +176,7 @@ When you visit `http://www.example.com/test.pl` in your browser, your Perl envir
You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
-- [The nginx Homepage](http://nginx.org/)
+- [The NGINX Homepage](http://nginx.org/)
- [FastCGI Project Homepage](http://www.fastcgi.com/)
- [Perl Documentation](http://perldoc.perl.org/)
-- [Basic Ngnix Configuration](/docs/websites/nginx/basic-nginx-configuration)
+- [Basic NGINX Configuration](/docs/websites/nginx/basic-nginx-configuration)
diff --git a/docs/web-servers/nginx/nginx-and-perlfastcgi-on-ubuntu-11-04-natty.md b/docs/web-servers/nginx/nginx-and-perlfastcgi-on-ubuntu-11-04-natty.md
index c9b4d487caa..1c8e5a018cd 100644
--- a/docs/web-servers/nginx/nginx-and-perlfastcgi-on-ubuntu-11-04-natty.md
+++ b/docs/web-servers/nginx/nginx-and-perlfastcgi-on-ubuntu-11-04-natty.md
@@ -175,7 +175,7 @@ When you visit `http://www.example.com/test.pl` in your browser, your Perl envir
You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
-- [The nginx Homepage](http://nginx.org/)
+- [The NGINX Homepage](http://nginx.org/)
- [FastCGI Project Homepage](http://www.fastcgi.com/)
- [Perl Documentation](http://perldoc.perl.org/)
-- [Basic Ngnix Configuration](/docs/websites/nginx/basic-nginx-configuration)
+- [Basic NGINX Configuration](/docs/websites/nginx/basic-nginx-configuration)
diff --git a/docs/web-servers/nginx/nginx-and-perlfastcgi-on-ubuntu-9-10-karmic.md b/docs/web-servers/nginx/nginx-and-perlfastcgi-on-ubuntu-9-10-karmic.md
index fd96e020b42..5519bd1bd57 100644
--- a/docs/web-servers/nginx/nginx-and-perlfastcgi-on-ubuntu-9-10-karmic.md
+++ b/docs/web-servers/nginx/nginx-and-perlfastcgi-on-ubuntu-9-10-karmic.md
@@ -167,8 +167,8 @@ When you visit `http://www.example.com/test.pl` in your browser, your Perl envir
You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
-- [The nginx Homepage](http://nginx.org/)
+- [The NGINX Homepage](http://nginx.org/)
- [FastCGI Project Homepage](http://www.fastcgi.com/)
- [Perl Documentation](http://perldoc.perl.org/)
-- [Installing Nginx on Ubuntu 9.10 (Karmic)](/docs/web-servers/nginx/installation/ubuntu-9-10-karmic)
-- [Basic Ngnix Configuration](/docs/websites/nginx/basic-nginx-configuration)
+- [Installing NGINX on Ubuntu 9.10 (Karmic)](/docs/web-servers/nginx/installation/ubuntu-9-10-karmic)
+- [Basic NGINX Configuration](/docs/websites/nginx/basic-nginx-configuration)
diff --git a/docs/web-servers/nginx/nginx-and-phpfastcgi-on-arch-linux.md b/docs/web-servers/nginx/nginx-and-phpfastcgi-on-arch-linux.md
index 4a840826c39..4ef988dd2d2 100644
--- a/docs/web-servers/nginx/nginx-and-phpfastcgi-on-arch-linux.md
+++ b/docs/web-servers/nginx/nginx-and-phpfastcgi-on-arch-linux.md
@@ -157,7 +157,7 @@ When you visit `http://www.example.com/test.php` in your browser, the standard "
You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
-- [The nginx Homepage](http://nginx.org/)
+- [The NGINX Homepage](http://nginx.org/)
- [FastCGI Project Homepage](http://www.fastcgi.com/)
- [PHP Documentation](http://www.php.net/docs.php)
-- [Basic Ngnix Configuration](/docs/websites/nginx/basic-nginx-configuration)
+- [Basic NGINX Configuration](/docs/websites/nginx/basic-nginx-configuration)
diff --git a/docs/web-servers/nginx/nginx-and-phpfastcgi-on-centos-5.md b/docs/web-servers/nginx/nginx-and-phpfastcgi-on-centos-5.md
index 747ac0bc2c5..e464f195df0 100644
--- a/docs/web-servers/nginx/nginx-and-phpfastcgi-on-centos-5.md
+++ b/docs/web-servers/nginx/nginx-and-phpfastcgi-on-centos-5.md
@@ -54,7 +54,7 @@ Issue the following commands to update your system and install the nginx web ser
chkconfig --level 35 nginx on
service nginx start
-You'll be asked to accept the key for EPEL, as it gets imported the first time you install an EPEL package. Various additional dependency packages will be installed along with the ones we requested. Once the installation process finishes, you may wish to make sure nginx is running by browsing to your Linode's IP address (found on the "Remote Access" tab in the [Linode Manager](http://manager.linode.com//)). You should get the default ngnix page.
+You'll be asked to accept the key for EPEL, as it gets imported the first time you install an EPEL package. Various additional dependency packages will be installed along with the ones we requested. Once the installation process finishes, you may wish to make sure nginx is running by browsing to your Linode's IP address (found on the "Remote Access" tab in the [Linode Manager](http://manager.linode.com/)). You should get the default NGINX page.
## Configure Your Site
diff --git a/docs/web-servers/nginx/nginx-and-phpfastcgi-on-debian-5-lenny.md b/docs/web-servers/nginx/nginx-and-phpfastcgi-on-debian-5-lenny.md
index 5a499dfc72c..c1e059a6609 100644
--- a/docs/web-servers/nginx/nginx-and-phpfastcgi-on-debian-5-lenny.md
+++ b/docs/web-servers/nginx/nginx-and-phpfastcgi-on-debian-5-lenny.md
@@ -36,7 +36,7 @@ Issue the following commands to update your system and install the nginx web ser
apt-get install nginx php5-cli php5-cgi build-essential wget psmisc
/etc/init.d/nginx start
-Various additional dependency packages will be installed along with the ones we requested. Once the installation process finishes, you may wish to make sure nginx is running by browsing to your Linode's IP address (found on the "Remote Access" tab in the [Linode Manager](http://manager.linode.com//)). You should get the default ngnix page.
+Various additional dependency packages will be installed along with the ones we requested. Once the installation process finishes, you may wish to make sure nginx is running by browsing to your Linode's IP address (found on the "Remote Access" tab in the [Linode Manager](http://manager.linode.com/)). You should get the default NGINX page.
# Configure Your Site
@@ -145,8 +145,8 @@ When you visit `http://www.example.com/test.php` in your browser, the standard "
You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
-- [The nginx Homepage](http://nginx.org/)
+- [The NGINX Homepage](http://nginx.org/)
- [FastCGI Project Homepage](http://www.fastcgi.com/)
- [PHP Documentation](http://www.php.net/docs.php)
- [Installing Nginx on Debian 5 (Lenny)](/docs/web-servers/nginx/installation/debian-5-lenny)
-- [Basic Ngnix Configuration](/docs/websites/nginx/basic-nginx-configuration)
+- [Basic NGINX Configuration](/docs/websites/nginx/basic-nginx-configuration)
diff --git a/docs/web-servers/nginx/nginx-and-phpfastcgi-on-debian-6-squeeze.md b/docs/web-servers/nginx/nginx-and-phpfastcgi-on-debian-6-squeeze.md
index 0eac712a7db..d7bfb7961aa 100644
--- a/docs/web-servers/nginx/nginx-and-phpfastcgi-on-debian-6-squeeze.md
+++ b/docs/web-servers/nginx/nginx-and-phpfastcgi-on-debian-6-squeeze.md
@@ -270,7 +270,7 @@ When you visit `http://www.example.com/test.php` in your browser, the standard "
You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
-- [The nginx Homepage](http://nginx.org/)
+- [The NGINX Homepage](http://nginx.org/)
- [FastCGI Project Homepage](http://www.fastcgi.com/)
- [PHP Documentation](http://www.php.net/docs.php)
-- [Basic Ngnix Configuration](/docs/websites/nginx/basic-nginx-configuration)
+- [Basic NGINX Configuration](/docs/websites/nginx/basic-nginx-configuration)
diff --git a/docs/web-servers/nginx/nginx-and-phpfastcgi-on-fedora-12.md b/docs/web-servers/nginx/nginx-and-phpfastcgi-on-fedora-12.md
index 62eb1fb0aa7..5c61676df58 100644
--- a/docs/web-servers/nginx/nginx-and-phpfastcgi-on-fedora-12.md
+++ b/docs/web-servers/nginx/nginx-and-phpfastcgi-on-fedora-12.md
@@ -44,7 +44,7 @@ Issue the following commands to update your system and install the nginx web ser
chkconfig --level 35 nginx on
service nginx start
-Once the installation process finishes, you may wish to make sure nginx is running by browsing to your Linode's IP address (found on the "Remote Access" tab in the [Linode Manager](http://manager.linode.com//)). You should get the default ngnix page.
+Once the installation process finishes, you may wish to make sure nginx is running by browsing to your Linode's IP address (found on the "Remote Access" tab in the [Linode Manager](http://manager.linode.com/)). You should get the default NGINX page.
# Configure Your Site
@@ -158,8 +158,8 @@ When you visit `http://www.example.com/test.php` in your browser, the standard "
You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
-- [The nginx Homepage](http://nginx.org/)
+- [The NGINX Homepage](http://nginx.org/)
- [FastCGI Project Homepage](http://www.fastcgi.com/)
- [PHP Documentation](http://www.php.net/docs.php)
-- [Installing Nginx on Fedora 12](/docs/web-servers/nginx/installation/fedora-12)
-- [Basic Ngnix Configuration](/docs/websites/nginx/basic-nginx-configuration)
+- [Installing NGINX on Fedora 12](/docs/web-servers/nginx/installation/fedora-12)
+- [Basic NGINX Configuration](/docs/websites/nginx/basic-nginx-configuration)
diff --git a/docs/web-servers/nginx/nginx-and-phpfastcgi-on-fedora-13.md b/docs/web-servers/nginx/nginx-and-phpfastcgi-on-fedora-13.md
index e53a2f3530f..9b032a8bc0d 100644
--- a/docs/web-servers/nginx/nginx-and-phpfastcgi-on-fedora-13.md
+++ b/docs/web-servers/nginx/nginx-and-phpfastcgi-on-fedora-13.md
@@ -44,7 +44,7 @@ Issue the following commands to update your system and install the nginx web ser
chkconfig --level 35 nginx on
service nginx start
-Once the installation process finishes, you may wish to make sure nginx is running by browsing to your Linode's IP address (found on the "Remote Access" tab in the [Linode Manager](http://manager.linode.com//)). You should get the default ngnix page.
+Once the installation process finishes, you may wish to make sure nginx is running by browsing to your Linode's IP address (found on the "Remote Access" tab in the [Linode Manager](http://manager.linode.com/)). You should get the default NGINX page.
# Configure Your Site
@@ -158,8 +158,8 @@ When you visit `http://www.example.com/test.php` in your browser, the standard "
You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
-- [The nginx Homepage](http://nginx.org/)
+- [The NGINX Homepage](http://nginx.org/)
- [FastCGI Project Homepage](http://www.fastcgi.com/)
- [PHP Documentation](http://www.php.net/docs.php)
-- [Installing Nginx on Fedora 13](/docs/web-servers/nginx/installation/fedora-13)
-- [Basic Ngnix Configuration](/docs/websites/nginx/basic-nginx-configuration)
+- [Installing NGINX on Fedora 13](/docs/web-servers/nginx/installation/fedora-13)
+- [Basic NGINX Configuration](/docs/websites/nginx/basic-nginx-configuration)
diff --git a/docs/web-servers/nginx/nginx-and-phpfastcgi-on-fedora-14.md b/docs/web-servers/nginx/nginx-and-phpfastcgi-on-fedora-14.md
index 5049421e799..521b25f7a23 100644
--- a/docs/web-servers/nginx/nginx-and-phpfastcgi-on-fedora-14.md
+++ b/docs/web-servers/nginx/nginx-and-phpfastcgi-on-fedora-14.md
@@ -37,7 +37,7 @@ Issue the following commands to update your system and install the nginx web ser
chkconfig --level 35 nginx on
service nginx start
-Once the installation process finishes, you may wish to make sure nginx is running by browsing to your Linode's IP address (found on the "Remote Access" tab in the [Linode Manager](http://manager.linode.com//)). You should get the default ngnix page.
+Once the installation process finishes, you may wish to make sure nginx is running by browsing to your Linode's IP address (found on the "Remote Access" tab in the [Linode Manager](http://manager.linode.com/)). You should get the default NGINX page.
# Configure Your Site
@@ -151,8 +151,8 @@ When you visit `http://www.example.com/test.php` in your browser, the standard "
You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
-- [The nginx Homepage](http://nginx.org/)
+- [The NGINX Homepage](http://nginx.org/)
- [FastCGI Project Homepage](http://www.fastcgi.com/)
- [PHP Documentation](http://www.php.net/docs.php)
-- [Installing Nginx on Fedora 14](/docs/web-servers/nginx/installation/fedora-14)
-- [Basic Ngnix Configuration](/docs/websites/nginx/basic-nginx-configuration)
+- [Installing NGINX on Fedora 14](/docs/web-servers/nginx/installation/fedora-14)
+- [Basic NGINX Configuration](/docs/websites/nginx/basic-nginx-configuration)
diff --git a/docs/web-servers/nginx/nginx-and-phpfastcgi-on-ubuntu-10-04-lts-lucid.md b/docs/web-servers/nginx/nginx-and-phpfastcgi-on-ubuntu-10-04-lts-lucid.md
index 1cd39c3241f..fe6b9a0b28c 100644
--- a/docs/web-servers/nginx/nginx-and-phpfastcgi-on-ubuntu-10-04-lts-lucid.md
+++ b/docs/web-servers/nginx/nginx-and-phpfastcgi-on-ubuntu-10-04-lts-lucid.md
@@ -270,7 +270,7 @@ When you visit `http://www.example.com/test.php` in your browser, the standard "
You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
-- [The nginx Homepage](http://nginx.org/)
+- [The NGINX Homepage](http://nginx.org/)
- [FastCGI Project Homepage](http://www.fastcgi.com/)
- [PHP Documentation](http://www.php.net/docs.php)
-- [Basic Ngnix Configuration](/docs/websites/nginx/basic-nginx-configuration)
+- [Basic NGINX Configuration](/docs/websites/nginx/basic-nginx-configuration)
diff --git a/docs/web-servers/nginx/nginx-and-phpfastcgi-on-ubuntu-10-10-maverick.md b/docs/web-servers/nginx/nginx-and-phpfastcgi-on-ubuntu-10-10-maverick.md
index 3d3269a3b0e..4575d10ceef 100644
--- a/docs/web-servers/nginx/nginx-and-phpfastcgi-on-ubuntu-10-10-maverick.md
+++ b/docs/web-servers/nginx/nginx-and-phpfastcgi-on-ubuntu-10-10-maverick.md
@@ -270,7 +270,7 @@ When you visit `http://www.example.com/test.php` in your browser, the standard "
You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
-- [The nginx Homepage](http://nginx.org/)
+- [The NGINX Homepage](http://nginx.org/)
- [FastCGI Project Homepage](http://www.fastcgi.com/)
- [PHP Documentation](http://www.php.net/docs.php)
-- [Basic Ngnix Configuration](/docs/websites/nginx/basic-nginx-configuration)
+- [Basic NGINX Configuration](/docs/websites/nginx/basic-nginx-configuration)
diff --git a/docs/web-servers/nginx/nginx-and-phpfastcgi-on-ubuntu-11-04-natty.md b/docs/web-servers/nginx/nginx-and-phpfastcgi-on-ubuntu-11-04-natty.md
index db2f4902a71..d5d43e8e313 100644
--- a/docs/web-servers/nginx/nginx-and-phpfastcgi-on-ubuntu-11-04-natty.md
+++ b/docs/web-servers/nginx/nginx-and-phpfastcgi-on-ubuntu-11-04-natty.md
@@ -270,7 +270,7 @@ When you visit `http://www.example.com/test.php` in your browser, the standard "
You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
-- [The nginx Homepage](http://nginx.org/)
+- [The NGINX Homepage](http://nginx.org/)
- [FastCGI Project Homepage](http://www.fastcgi.com/)
- [PHP Documentation](http://www.php.net/docs.php)
-- [Basic Ngnix Configuration](/docs/websites/nginx/basic-nginx-configuration)
+- [Basic NGINX Configuration](/docs/websites/nginx/basic-nginx-configuration)
diff --git a/docs/web-servers/nginx/nginx-and-phpfastcgi-on-ubuntu-9-10-karmic.md b/docs/web-servers/nginx/nginx-and-phpfastcgi-on-ubuntu-9-10-karmic.md
index 4c010fcd78f..9b023ea3d9b 100644
--- a/docs/web-servers/nginx/nginx-and-phpfastcgi-on-ubuntu-9-10-karmic.md
+++ b/docs/web-servers/nginx/nginx-and-phpfastcgi-on-ubuntu-9-10-karmic.md
@@ -60,7 +60,7 @@ Issue the following commands to update your system and install the nginx web ser
apt-get upgrade
apt-get install nginx php5-cli php5-cgi spawn-fcgi
-Various additional dependency packages will be installed along with the ones we requested. Once the installation process finishes, you may wish to make sure nginx is running by browsing to your Linode's IP address (found on the "Remote Access" tab in the [Linode Manager](http://manager.linode.com//)). You should get the default ngnix page.
+Various additional dependency packages will be installed along with the ones we requested. Once the installation process finishes, you may wish to make sure nginx is running by browsing to your Linode's IP address (found on the "Remote Access" tab in the [Linode Manager](http://manager.linode.com/)). You should get the default NGINX page.
# Configure Your Site
@@ -165,8 +165,8 @@ When you visit `http://www.example.com/test.php` in your browser, the standard "
You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
-- [The nginx Homepage](http://nginx.org/)
+- [The NGINX Homepage](http://nginx.org/)
- [FastCGI Project Homepage](http://www.fastcgi.com/)
- [PHP Documentation](http://www.php.net/docs.php)
- [Installing Nginx on Ubuntu 9.10 (Karmic)](/docs/web-servers/nginx/installation/ubuntu-9-10-karmic)
-- [Basic Ngnix Configuration](/docs/websites/nginx/basic-nginx-configuration)
+- [Basic NGINX Configuration](/docs/websites/nginx/basic-nginx-configuration)
diff --git a/docs/web-servers/nginx/nginx-reverse-proxy.md b/docs/web-servers/nginx/nginx-reverse-proxy.md
index 350f6cabf42..0d8708aa09a 100644
--- a/docs/web-servers/nginx/nginx-reverse-proxy.md
+++ b/docs/web-servers/nginx/nginx-reverse-proxy.md
@@ -81,7 +81,7 @@ The sample app will use the `http.server` module (available for Python 3.4 and a
{{< note >}}
Python 2.7 has an equivalent module via `python -m SimpleHTTPServer 8000` that listens to all interfaces but does not have an option to bind to a specific address from the command line.
-Using the `http.server` module from Python 3.4 and above is highly recommanded as it allows a convenient way to bind to a specific IP. Some distributions may need to specify the Python version explicitly: `python3 -m http.server 8000 --bind 127.0.0.1`
+Using the `http.server` module from Python 3.4 and above is highly recommended as it allows a convenient way to bind to a specific IP. Some distributions may need to specify the Python version explicitly: `python3 -m http.server 8000 --bind 127.0.0.1`
{{< /note >}}
4. Open a new terminal. Use `curl` to check the HTTP headers:
diff --git a/docs/web-servers/nginx/nginx-ssl-and-tls-deployment-best-practices.md b/docs/web-servers/nginx/nginx-ssl-and-tls-deployment-best-practices.md
index 9d11fb46925..12eb7ff3c92 100644
--- a/docs/web-servers/nginx/nginx-ssl-and-tls-deployment-best-practices.md
+++ b/docs/web-servers/nginx/nginx-ssl-and-tls-deployment-best-practices.md
@@ -10,7 +10,7 @@ published: 2016-08-18
modified: 2016-08-18
modified_by:
name: Linode
-title: 'Nginx SSL and TLS Deployment Best Practices'
+title: 'NGINX SSL and TLS Deployment Best Practices'
contributor:
name: Ryan Laverdiere
link: https://github.com/capecodrailfan
@@ -19,11 +19,11 @@ external_resources:
- '[KeyCDN HTTP/2 Test](https://tools.keycdn.com/http2-test)'
---
-This guide is intended to inform you of some additional configuration options that nginx uses when serving HTTPS. While these features help optimize nginx for SSL and TLS, this is by no means a complete guide to securing nginx or your Linode. The best way to ensure your server remains secure is to not only configure it properly, but to follow best security practices at all times. This guide is intended to be one of many steps toward creating the most secure environment possible.
+This guide is intended to inform you of some additional configuration options that NGINX uses when serving HTTPS. While these features help optimize NGINX for SSL and TLS, this is by no means a complete guide to securing NGINX or your Linode. The best way to ensure your server remains secure is to not only configure it properly, but to follow best security practices at all times. This guide is intended to be one of many steps toward creating the most secure environment possible.
## Before you Begin
-1. This guide is a continuation of our tutorial on how to [install nginx and a StartSSL certificate on Debian 8 (Jessie)](/docs/websites/nginx/install-nginx-and-a-startssl-certificate-on-debian-8-jessie). The principles here can be adapted to an SSL/TLS deployment on any system, but at a minimum, you will need a Linode with the latest stable version of nginx and an SSL certificate installed.
+1. This guide is a continuation of our tutorial on how to [install NGINX and a StartSSL certificate on Debian 8 (Jessie)](/docs/websites/nginx/install-nginx-and-a-startssl-certificate-on-debian-8-jessie). The principles here can be adapted to an SSL/TLS deployment on any system, but at a minimum, you will need a Linode with the latest stable version of NGINX and an SSL certificate installed.
2. Update your system:
@@ -33,13 +33,13 @@ This guide is intended to inform you of some additional configuration options th
The commands in this guide are written for a root user. If you're following along as a non-root user, commands that require elevated privileges should prefixed with `sudo`. If you’re not familiar with the `sudo` command, you can check our [Users and Groups](/docs/tools-reference/linux-users-and-groups) guide.
{{< /note >}}
-For more information, please review our guides on [basic nginx configuration](/docs/websites/nginx/how-to-configure-nginx), [Linux security basics](/docs/security/linux-security-basics) and [securing your server](/docs/security/securing-your-server).
+For more information, please review our guides on [basic NGINX configuration](/docs/websites/nginx/how-to-configure-nginx), [Linux security basics](/docs/security/linux-security-basics) and [securing your server](/docs/security/securing-your-server).
-## Disable nginx Server Tokens
+## Disable NGINX Server Tokens
-By default, nginx will share its version number with anyone who connects to your server. For example, if a directory is not found, nginx will return a 404 error that includes its version number. Disabling server tokens makes it more difficult to determine the version of nginx running on your Linode, and therefore more difficult to implement version-specific exploits.
+By default, NGINX will share its version number with anyone who connects to your server. For example, if a directory is not found, NGINX will return a 404 error that includes its version number. Disabling server tokens makes it more difficult to determine the version of NGINX running on your Linode, and therefore more difficult to implement version-specific exploits.
-[](/docs/assets/404_Not_Found.jpg)
+[](/docs/assets/404_Not_Found.jpg)
1. To disable `server_tokens`, open your `/etc/nginx/nginx.conf` file. Inside of the `http` block, append or uncomment the following line:
@@ -49,33 +49,33 @@ server_tokens off;
{{< /file-excerpt >}}
-2. Save your changes and restart nginx.
+2. Save your changes and restart NGINX.
systemctl restart nginx
-After restarting, direct your web browser to a directory of your server that does not exist, and nginx will no longer share its version number.
+After restarting, direct your web browser to a directory of your server that does not exist, and NGINX will no longer share its version number.
[](/docs/assets/404_Not_Found_Server_Tokens_Off.jpg)
## Enable HTTP/2 Support
-In September 2010, Google released the SPDY protocol for all versions of Chrome 6. SPDY is currently being phased out in favor of HTTP/2. Support for SPDY in Chrome was removed in May 2016. SPDY is supported only in nginx 1.8.x or older, whereas versions beginning with 1.9.5 are beginning to support HTTP/2. To check your nginx version:
+In September 2010, Google released the SPDY protocol for all versions of Chrome 6. SPDY is currently being phased out in favor of HTTP/2. Support for SPDY in Chrome was removed in May 2016. SPDY is supported only in NGINX 1.8.x or older, whereas versions beginning with 1.9.5 are beginning to support HTTP/2. To check your NGINX version:
nginx -v
{{< note >}}
-If you installed nginx from source without modifying your environment variables, invoke the full path to the binary:
+If you installed NGINX from source without modifying your environment variables, invoke the full path to the binary:
/opt/nginx/sbin/nginx -v
{{< /note >}}
-HTTP/2 is a new version of the HTTP standard replacing HTTP/1.1 to reduce page load time. Traditionally, when a user accessed a web page, a separate HTTP connection was established to load each resource (e.g. HTML, CSS, JavaScript, or images). HTTP/2 allows concurrent requests on a single connection to download assests in parallel. The server also compresses assets before sending them to the client, which requires less bandwdith.
+HTTP/2 is a new version of the HTTP standard replacing HTTP/1.1 to reduce page load time. Traditionally, when a user accessed a web page, a separate HTTP connection was established to load each resource (e.g. HTML, CSS, JavaScript, or images). HTTP/2 allows concurrent requests on a single connection to download assets in parallel. The server also compresses assets before sending them to the client, which requires less bandwidth.
{{< note >}}
-Chrome has deprecated Next Protocol Negotiation (NPN) and now requires Application-Layer Protocol Negotiation (ALPN) for HTTP/2 compatibility. However, ALPN requires OpenSSL 1.0.2+. Many distributions, such as Debian 8 (Jessie) do not include this package in their repositories. If you intend to enable HTTP/2, you will need to use a version of nginx compiled with OpenSSL 1.0.2+. See our instructions on [compiling nginx from source](/docs/web-servers/nginx/install-nginx-and-a-startssl-certificate-on-debian-8-jessie/#install-and-compile-nginx-from-source) for more information.
+Chrome has deprecated Next Protocol Negotiation (NPN) and now requires Application-Layer Protocol Negotiation (ALPN) for HTTP/2 compatibility. However, ALPN requires OpenSSL 1.0.2+. Many distributions, such as Debian 8 (Jessie) do not include this package in their repositories. If you intend to enable HTTP/2, you will need to use a version of NGINX compiled with OpenSSL 1.0.2+. See our instructions on [compiling NGINX from source](/docs/web-servers/nginx/install-nginx-and-a-startssl-certificate-on-debian-8-jessie/#install-and-compile-nginx-from-source) for more information.
{{< /note >}}
-1. To enable HTTP/2, open your nginx SSL virtual host configuration file. Depending on how you installed nginx, this could be located at `/etc/nginx/sites-enabled/default` or at `/etc/nginx/conf.d/example_ssl.conf`. Look for the `listen` line within the "SSL Configuration" section. Uncomment the following line if necessary and add `http2` to the end before the semicolon.
+1. To enable HTTP/2, open your NGINX SSL virtual host configuration file. Depending on how you installed NGINX, this could be located at `/etc/nginx/sites-enabled/default` or at `/etc/nginx/conf.d/example_ssl.conf`. Look for the `listen` line within the "SSL Configuration" section. Uncomment the following line if necessary and add `http2` to the end before the semicolon.
{{< file-excerpt "/etc/nginx/conf.d/example_ssl.conf" aconf >}}
listen 443 ssl http2;
@@ -83,7 +83,7 @@ listen 443 ssl http2;
{{< /file-excerpt >}}
-2. Save your changes and restart nginx.
+2. Save your changes and restart NGINX.
systemctl restart nginx
@@ -97,9 +97,9 @@ listen 443 ssl http2;
Google is now ranking websites that accept encrypted HTTPS connections higher in search results, so redirecting HTTP requests to HTTPS is one possible way to increase your page rank. Before following these steps, however, be sure to research compatibility issues that may arise with older browsers.
-1. Open your HTTP nginx virtual host configuration file, which can be located at `/etc/nginx/conf.d/default.conf`, `/etc/nginx/nginx.conf` or `/etc/nginx/sites-enabled/default` depending on how you installed nginx. Change `example.com` to match your Linode's domain name or hostname:
+1. Open your HTTP NGINX virtual host configuration file, which can be located at `/etc/nginx/conf.d/default.conf`, `/etc/nginx/nginx.conf` or `/etc/nginx/sites-enabled/default` depending on how you installed nginx. Change `example.com` to match your Linode's domain name or hostname:
- {{< file-excerpt "/etc/nginx/conf.d/default.conf" aconf >}}
+ {{< file-excerpt "/etc/nginx/conf.d/default.conf" nginx >}}
server_name example.com
{{< /file-excerpt >}}
@@ -107,7 +107,7 @@ server_name example.com
2. Append the following line below the `server_name` line.
- {{< file-excerpt "/etc/nginx/conf.d/default.conf" aconf >}}
+ {{< file-excerpt "/etc/nginx/conf.d/default.conf" nginx >}}
rewrite ^ https://$server_name$request_uri? permanent;
{{< /file-excerpt >}}
@@ -115,7 +115,7 @@ rewrite ^ https://$server_name$request_uri? permanent;
3. Comment out (place `#` in front of) all other lines so your configuration looks like this:
- {{< file-excerpt "/etc/nginx/conf.d/default.conf" aconf >}}
+ {{< file-excerpt "/etc/nginx/conf.d/default.conf" nginx >}}
server {
listen 80;
server_name example.com;
@@ -125,7 +125,7 @@ server {
{{< /file-excerpt >}}
-4. Save your changes and restart nginx.
+4. Save your changes and restart NGINX.
systemctl restart nginx
@@ -137,13 +137,13 @@ The *Online Certificate Status Protocol* (OCSP) was created to speed up the proc
The problem with OCSP is that a certificate authority can now track users as they move from website to website with certificates provided by the same vendor or certificate authority. To prevent this, you can enable OCSP stapling.
-When OCSP stapling is enabled, nginx on your Linode will make an OCSP request for the client. The response recieved from the OCSP server is added to nginx's reponse to the user. This eliminates the need for the user to connect to an OCSP server to check the revocation status of your server certificate.
+When OCSP stapling is enabled, NGINX on your Linode will make an OCSP request for the client. The response received from the OCSP server is added to NGINX's response to the user. This eliminates the need for the user to connect to an OCSP server to check the revocation status of your server certificate.
-Before enabling OCSP stapling you will need to have a file on your system that stores the CA certificates used to sign the server certificate. This section assumes that you have followed our guide on [how to install nginx and a StartSSL certificate](/docs/websites/nginx/install-nginx-and-a-startssl-certificate-on-debian-8-jessie). If you have not, complete Steps 1-3 in the [Gather Additional Required Certificate Files](/docs/web-servers/nginx/install-nginx-and-a-startssl-certificate-on-debian-8-jessie/#gather-additional-required-certificate-files) section of that guide before proceeding here.
+Before enabling OCSP stapling you will need to have a file on your system that stores the CA certificates used to sign the server certificate. This section assumes that you have followed our guide on [how to install NGINX and a StartSSL certificate](/docs/websites/nginx/install-nginx-and-a-startssl-certificate-on-debian-8-jessie). If you have not, complete Steps 1-3 in the [Gather Additional Required Certificate Files](/docs/web-servers/nginx/install-nginx-and-a-startssl-certificate-on-debian-8-jessie/#gather-additional-required-certificate-files) section of that guide before proceeding here.
-1. Open your HTTPS nginx virtual host configuration file, which can be located at `/etc/nginx/conf.d/example_ssl.conf` or `/etc/nginx/sites-enabled/default` depending on how you installed and configured nginx. Add the following lines inside the `server` block:
+1. Open your HTTPS NGINX virtual host configuration file, which can be located at `/etc/nginx/conf.d/example_ssl.conf` or `/etc/nginx/sites-enabled/default` depending on how you installed and configured NGINX. Add the following lines inside the `server` block:
- {{< file-excerpt "/etc/nginx/conf.d/example_ssl.conf" aconf >}}
+ {{< file-excerpt "/etc/nginx/conf.d/example_ssl.conf" nginx >}}
ssl_stapling on;
ssl_stapling_verify on;
ssl_trusted_certificate /etc/ssl/nginx/ca.pem;
@@ -151,7 +151,7 @@ ssl_trusted_certificate /etc/ssl/nginx/ca.pem;
{{< /file-excerpt >}}
-2. Save your changes and restart nginx.
+2. Save your changes and restart NGINX.
systemctl restart nginx
@@ -171,7 +171,7 @@ With all traffic being redirected from HTTP to HTTPS, you may want to allow user
1. Open up your nginx HTTPS virtual host configuration file. This may be located at `/etc/nginx/sites-enabled/default` or at `/etc/nginx/conf.d/example_ssl.conf`. Append the following line inside your `server` block:
- {{< file-excerpt "/etc/nginx/conf.d/example_ssl.conf" aconf >}}
+ {{< file-excerpt "/etc/nginx/conf.d/example_ssl.conf" nginx >}}
add_header Strict-Transport-Security "max-age=31536000; includeSubdomains";
{{< /file-excerpt >}}
@@ -179,7 +179,7 @@ add_header Strict-Transport-Security "max-age=31536000; includeSubdomains";
The `max-age` attribute sets the expiration date for this header in seconds; in the above configuration, the header will expire after 1 year. You can configure this to be longer or shorter if you choose, but a period of less than 180 days is considered too short for the Qualys test. The `includeSubdomains` argument enforces HSTS on all subdomains.
-2. Save your changes and restart nginx.
+2. Save your changes and restart NGINX.
systemctl restart nginx
@@ -189,15 +189,15 @@ add_header Strict-Transport-Security "max-age=31536000; includeSubdomains";
If you've already conducted a test from one of the above sections, use the **Clear cache** link to initiate a new scan.
{{< /note >}}
- Once the test is complete, scroll down to the "Protocol Details" section. Look for the "Strict Transport Security (HSTS)" line. If nginx is configured correctly this test will return "Yes."
+ Once the test is complete, scroll down to the "Protocol Details" section. Look for the "Strict Transport Security (HSTS)" line. If NGINX is configured correctly this test will return "Yes."
[](/docs/assets/HSTS_SSL_Test.jpg)
## Disable Content Sniffing
-Content sniffing allows browsers to inspect a byte stream in order to "guess" the file format of its contents. It is generally used to help sites that do not correctly identify the MIME type of their web content, but it also presents a vulnerability to cross-site scripting and other attacks. To disable content sniffing, add the following line to your nginx SSL configuration file in the `server` block:
+Content sniffing allows browsers to inspect a byte stream in order to "guess" the file format of its contents. It is generally used to help sites that do not correctly identify the MIME type of their web content, but it also presents a vulnerability to cross-site scripting and other attacks. To disable content sniffing, add the following line to your NGINX SSL configuration file in the `server` block:
-{{< file "/etc/nginx/conf.d/example_ssl.conf" aconf >}}
+{{< file "/etc/nginx/conf.d/example_ssl.conf" nginx >}}
add_header X-Content-Type-Options nosniff;
{{< /file >}}
@@ -207,7 +207,7 @@ add_header X-Content-Type-Options nosniff;
The HTTPS header `X-Frame-Options` can specify whether a page is able to be rendered in a frame, iframe, or object. If left unset, your site's content may be embedded into other sites' HTML code in a clickjacking attack. To disable the embedding of your content, add the following line to your SSL configuration file in the `server` block:
-{{< file "/etc/nginx/conf.d/example_ssl.conf" aconf >}}
+{{< file "/etc/nginx/conf.d/example_ssl.conf" nginx >}}
add_header X-Frame-Options DENY;
{{< /file >}}
@@ -227,23 +227,23 @@ We're using a 4096-bit RSA private key to sign the Diffie-Hellman key exchange,
openssl dhparam -out dhparam.pem 4096
-3. Specify the new parameter by adding the following line to your nginx SSL configuration file in the `server` block:
+3. Specify the new parameter by adding the following line to your NGINX SSL configuration file in the `server` block:
- {{< file "/etc/nginx/conf.d/example_ssl.conf" aconf >}}
+ {{< file "/etc/nginx/conf.d/example_ssl.conf" nginx >}}
ssl_dhparam /etc/ssl/certs/dhparam.pem;
{{< /file >}}
-4. Save your changes and restart nginx:
+4. Save your changes and restart NGINX:
systemctl restart nginx
## Test Your Configuration
-If you have been following along, starting with the guide on installing the latest version of nginx for Debian Wheezy or Jessie and getting a StartSSL certificate, your `/etc/nginx/conf.d/example_ssl.conf` should now look similar to this:
+If you have been following along, starting with the guide on installing the latest version of NGINX for Debian Wheezy or Jessie and getting a StartSSL certificate, your `/etc/nginx/conf.d/example_ssl.conf` should now look similar to this:
-{{< file "/etc/nginx/conf.d/example_ssl.conf" aconf >}}
+{{< file "/etc/nginx/conf.d/example_ssl.conf" nginx >}}
# HTTPS server
#
server {
@@ -281,6 +281,6 @@ server {
{{< /file >}}
-Now that you've optimized nginx for SSL and TLS, you can test your configuration at [Qualys SSL Labs SSL Server Test](https://www.ssllabs.com/ssltest/). This configuration should earn you a grade of "A+." If you are getting a lesser rating, check your configuration for errors. Additionally, check that your site is enabled and returning a 200 HTTP response code, as that may also affect your rating. This information can be found in the "Miscellaneous" section at the bottom of your SSL Server Test report.
+Now that you've optimized NGINX for SSL and TLS, you can test your configuration at [Qualys SSL Labs SSL Server Test](https://www.ssllabs.com/ssltest/). This configuration should earn you a grade of "A+." If you are getting a lesser rating, check your configuration for errors. Additionally, check that your site is enabled and returning a 200 HTTP response code, as that may also affect your rating. This information can be found in the "Miscellaneous" section at the bottom of your SSL Server Test report.
Again, the best way to ensure security is by following best practices at all times, not simply relying on your configuration, so be sure to monitor for updates and apply them to your server as needed. With proper maintenance, your server will remain secure and safe from attack.
diff --git a/docs/web-servers/nginx/use-uwsgi-to-deploy-python-apps-with-nginx-on-ubuntu-12-04.md b/docs/web-servers/nginx/use-uwsgi-to-deploy-python-apps-with-nginx-on-ubuntu-12-04.md
index af3409b465e..bc38905f9c6 100644
--- a/docs/web-servers/nginx/use-uwsgi-to-deploy-python-apps-with-nginx-on-ubuntu-12-04.md
+++ b/docs/web-servers/nginx/use-uwsgi-to-deploy-python-apps-with-nginx-on-ubuntu-12-04.md
@@ -157,7 +157,7 @@ def application(environ, start_response):
service nginx restart
-You can test by pointing a web browser to your domian. If you see `Hello World!` than you have successfully configured your Linode for uWSGI with Nginx!
+You can test by pointing a web browser to your domain. If you see `Hello World!` than you have successfully configured your Linode for uWSGI with Nginx!
# Additional Application Servers
diff --git a/docs/websites/cms/install-and-configure-drupal-8.md b/docs/websites/cms/install-and-configure-drupal-8.md
index bbb1192633d..ab4142ab6e7 100644
--- a/docs/websites/cms/install-and-configure-drupal-8.md
+++ b/docs/websites/cms/install-and-configure-drupal-8.md
@@ -21,7 +21,7 @@ Drupal 8 is the lastest version of the popular [Drupal](https://www.drupal.org/)
1. Familiarize yourself with our [Getting Started](/docs/getting-started) guide and complete the steps for setting your Linode's hostname and timezone.
-2. This guide will use `sudo` wherever possible. Complete the sections of our [Securing Your Server](/docs/security/securing-your-server) guide to create a standard user account, harden SSH access, remove unnecessary network services and create firewall rules for your web server; you may need to make addional firewall exceptions for your specific application.
+2. This guide will use `sudo` wherever possible. Complete the sections of our [Securing Your Server](/docs/security/securing-your-server) guide to create a standard user account, harden SSH access, remove unnecessary network services and create firewall rules for your web server; you may need to make additional firewall exceptions for your specific application.
3. Update your system:
diff --git a/docs/websites/cms/install-odoo-10-on-ubuntu-16-04.md b/docs/websites/cms/install-odoo-10-on-ubuntu-16-04.md
old mode 100755
new mode 100644
index 5706ed5d853..32ca4489bca
--- a/docs/websites/cms/install-odoo-10-on-ubuntu-16-04.md
+++ b/docs/websites/cms/install-odoo-10-on-ubuntu-16-04.md
@@ -331,7 +331,7 @@ Clone the updated Odoo source which is different from your older production inst
The advantage of using the same server is that all dependencies have already been met. What is next is to configure the server accordingly.
-1. Copy the original configuration file from the source to appropiate location:
+1. Copy the original configuration file from the source to appropriate location:
sudo cp /opt/odoo/debian/odoo.conf /etc/odoo-server-te.conf
diff --git a/docs/websites/cms/manage-web-content-with-joomla.md b/docs/websites/cms/manage-web-content-with-joomla.md
index 1a3aa74b139..eeac1be1857 100644
--- a/docs/websites/cms/manage-web-content-with-joomla.md
+++ b/docs/websites/cms/manage-web-content-with-joomla.md
@@ -20,7 +20,7 @@ Before installing Joomla, we assume that you have followed our [getting started
## Installing Prerequisites
-After installing the [LAMP stack](/docs/lamp-guides/), you must attend to a few additional prerequsites to complete this Joomla installation. Ensure that your distribution provides `wget` and `unzip` tools. In Debian- and Ubuntu-based systems, issue the following command:
+After installing the [LAMP stack](/docs/lamp-guides/), you must attend to a few additional prerequisites to complete this Joomla installation. Ensure that your distribution provides `wget` and `unzip` tools. In Debian- and Ubuntu-based systems, issue the following command:
apt-get update
apt-get upgrade --show-upgraded
diff --git a/docs/websites/cms/themes-modules-backups-drupal-drush-on-debian-7.md b/docs/websites/cms/themes-modules-backups-drupal-drush-on-debian-7.md
index 84330f78024..eff7e550c7b 100644
--- a/docs/websites/cms/themes-modules-backups-drupal-drush-on-debian-7.md
+++ b/docs/websites/cms/themes-modules-backups-drupal-drush-on-debian-7.md
@@ -22,17 +22,17 @@ Linode has another guide for installing Drush and creating a Drupal website, [In
Before installing themes, modules, and a backup system with Drush, make sure that the following prerequisites have been met:
-1. Create a new Linode by following our [Getting Started](/docs/getting-started/) guide.
+1. Create a new Linode by following our [Getting Started](/docs/getting-started/) guide.
-2. Address security concerns with the [Securing Your Server](/docs/securing-your-server) guide.
+2. Address security concerns with the [Securing Your Server](/docs/securing-your-server) guide.
-3. Configure a LAMP stack using the [Hosting a Website](/docs/websites/hosting-a-website) guide.
+3. Configure a LAMP stack using the [Hosting a Website](/docs/websites/hosting-a-website) guide.
-4. Install Drush and a Drupal website core with the [Installing & Using Drupal Drush on Debian 7](/docs/websites/cms/drush-drupal) guide.
+4. Install Drush and a Drupal website core with the [Installing & Using Drupal Drush on Debian 7](/docs/websites/cms/drush-drupal) guide.
-5. Make sure that your system is up to date, using:
+5. Make sure that your system is up to date, using:
- sudo apt-get update && sudo apt-get upgrade
+ sudo apt-get update && sudo apt-get upgrade
{{< note >}}
@@ -43,49 +43,49 @@ This guide is written for a non-root user. Commands that require elevated privil
Downloading, enabling, and setting the theme is extremely easy with Drupal Drush.
-1. Find a theme to download. The Drush download name is usually in the release notes under the "Downloads" section on any drupal.org/project/project_theme theme page. Spaces are either removed or replaced with an underscore. Pictured below is an example. Here, "corporateclean" would be used in the Drush command:
+1. Find a theme to download. The Drush download name is usually in the release notes under the "Downloads" section on any drupal.org/project/project_theme theme page. Spaces are either removed or replaced with an underscore. Pictured below is an example. Here, "corporateclean" would be used in the Drush command:
[](/docs/assets/corporate-clean-drupal-theme-name.png)
- {{< note >}}
+ {{< note >}}
At the time of this guide's publication, this theme is not yet available for Drupal 8 beta. If you're using this version of Drupal, select another theme to replace Corporate Clean for this example.
{{< /note >}}
-2. While logged in as the website owner, download and enable the theme:
+2. While logged in as the website owner, download and enable the theme:
- drush en corporateclean -y
+ drush en corporateclean -y
- {{< note >}}
+ {{< note >}}
Notice the warning that "corporateclean was not found." The `drush en` command looks for the theme or module locally before downloading.
{{< /note >}}
-3. Set Corporate Clean as the default, active theme:
+3. Set Corporate Clean as the default, active theme:
- drush vset theme_default corporateclean
+ drush vset theme_default corporateclean
- Check the homepage of your site and the new theme should appear.
+ Check the homepage of your site and the new theme should appear.
## Installing Modules with Drush
Downloading and enabling a module is similar to working with a theme. However, modules can be used for almost any purpose. From enhancing public-facing functionality to providing a better administrative UI, there are thousands of Drupal modules. Try to find modules with clear documentation. Once installed, the browser interface can still be challenging.
-1. To download a popular module called Commerce, first install the supporting modules. There are several:
+1. To download a popular module called Commerce, first install the supporting modules. There are several:
- drush en addressfield ctools entity rules token views views_ui -y
+ drush en addressfield ctools entity rules token views views_ui -y
-2. Now that the supporting modules have been installed, download and enable Commerce:
+2. Now that the supporting modules have been installed, download and enable Commerce:
- drush en commerce -y
+ drush en commerce -y
- {{< note >}}
+ {{< note >}}
Notice that Commerce includes 21 sub-modules. Each has its own functionality and most have a control switch within the admin's browser interface.
{{< /note >}}
-3. Sign in to the Drupal browser interface and click on the "Modules" selection.
+3. Sign in to the Drupal browser interface and click on the "Modules" selection.
[](/docs/assets/drupal-modules-selection.png)
-4. Next, scroll down to the "Commerce" module set, pictured below. Start checking or turning on the different Commerce sub-modules. Finally, select the "Save configuration" button at the very bottom of the page.
+4. Next, scroll down to the "Commerce" module set, pictured below. Start checking or turning on the different Commerce sub-modules. Finally, select the "Save configuration" button at the very bottom of the page.
[](/docs/assets/drupal-modules-page.png)
@@ -93,21 +93,21 @@ You have successfully installed and turned on a new module. The module is now ru
## Backup a Drupal Site with Drush
-It's always important to keep regular backups of a website. Backups protect you from losing data due to configuration changes, vulnerabilites, or system failures. Backups should be stored on a separate system whenever possible. Drush has built-in tools to help create backups of your site.
+It's always important to keep regular backups of a website. Backups protect you from losing data due to configuration changes, vulnerabilities, or system failures. Backups should be stored on a separate system whenever possible. Drush has built-in tools to help create backups of your site.
-1. While in the `/drupal` directory, create a .tar.gz back-up file containing the site database and site files with:
+1. While in the `/drupal` directory, create a .tar.gz back-up file containing the site database and site files with:
- drush archive-dump
+ drush archive-dump
*The site has been backed up locally.* Notice the backup has been created and placed in the `/home/user/drush-backups/archive-dump/` directory in a folder time stamped with its creation time. Drush saves your data into a .tar.gz archive file, containing the Drupal site folder and a copy of the MySql database.
-2. To copy the file to a remote backup location, use the rsync command. Replace the `date-time-stamp`, `examplesitename.date-time-stamp.tar.gz`, `user`, `ip-address`, and `/user/` with the appropriate inputs:
+2. To copy the file to a remote backup location, use the rsync command. Replace the `date-time-stamp`, `examplesitename.date-time-stamp.tar.gz`, `user`, `ip-address`, and `/user/` with the appropriate inputs:
- rsync -avz /home/user/drush-backups/achive-dump/date-time-stamp/examplesitename.date-time-stamp.tar.gz user@ip-address:/home/user/
+ rsync -avz /home/user/drush-backups/archive-dump/date-time-stamp/examplesitename.date-time-stamp.tar.gz user@ip-address:/home/user/
-3. To revert back to a previously saved version of your site:
+3. To revert back to a previously saved version of your site:
- drush archive-restore /home/user/drush-backups/achive-dump/date-time-stamp/examplesitename.date-time-stamp.tar.gz
+ drush archive-restore /home/user/drush-backups/archive-dump/date-time-stamp/examplesitename.date-time-stamp.tar.gz
This will recreate the `drupal` folder, which you can then manually move into your web directory.
@@ -115,11 +115,11 @@ It's always important to keep regular backups of a website. Backups protect you
The backup process above can be automated. You must create an SHH Pair Key, a Bash script, and use Cron automation.
-1. Create SSH Key Pair Authentication *without a password* for the Linode hosting your Drupal site, and pass the public key to the backup server. This is a simple task. It's covered in the Using [SSH Key Pair Authentication](/docs/security/securing-your-server#create-an-authentication-key-pair) section of the [Securing Your Server](/docs/security/securing-your-server) guide.
+1. Create SSH Key Pair Authentication *without a password* for the Linode hosting your Drupal site, and pass the public key to the backup server. This is a simple task. It's covered in the Using [SSH Key Pair Authentication](/docs/security/securing-your-server#create-an-authentication-key-pair) section of the [Securing Your Server](/docs/security/securing-your-server) guide.
-2. On the Drupal hosting Linode, create a Bash script file. In the file excerpt below, replace `example.com` and the rsync command inputs from step 2 above:
+2. On the Drupal hosting Linode, create a Bash script file. In the file excerpt below, replace `example.com` and the rsync command inputs from step 2 above:
- nano drupal-backup.sh
+ nano drupal-backup.sh
{{< file "~/drupal-backup.sh" >}}
#!/bin/bash
@@ -131,13 +131,13 @@ rsync -avz /home/local-user/drush-backups/archive-dump/ remote-user@remote-ip-ad
{{< /file >}}
-3. Make the script file executable:
+3. Make the script file executable:
- chmod +x drupal-backup.sh
+ chmod +x drupal-backup.sh
-4. Open and edit the Crontab file:
+4. Open and edit the Crontab file:
- crontab -e
+ crontab -e
{{< file-excerpt "/tmp/crontab.A6VByT/crontab" >}}
# For example, you can run a backup of all your user accounts
@@ -152,9 +152,9 @@ rsync -avz /home/local-user/drush-backups/archive-dump/ remote-user@remote-ip-ad
{{< /file-excerpt >}}
- This back up configuration creates a saved version once a week. The Cron timer is set for 12:01 a.m. every Sunday. There are many ways to configure a back up with additional options to consider. Check our [Cron](/docs/tools-reference/tools/schedule-tasks-with-cron) guide for more information.
+ This back up configuration creates a saved version once a week. The Cron timer is set for 12:01 a.m. every Sunday. There are many ways to configure a back up with additional options to consider. Check our [Cron](/docs/tools-reference/tools/schedule-tasks-with-cron) guide for more information.
- This backup system leaves saved versions of the site and database on both the local and remote Linodes. Depending on the disk size of your Linode, you may want to occasionally delete older backup versions. The deletion task could be automated within the Bash script above. Since the Cron timer is only set for once a week, disk usage is probably not a large concern. There are many configuration options to consider.
+ This backup system leaves saved versions of the site and database on both the local and remote Linodes. Depending on the disk size of your Linode, you may want to occasionally delete older backup versions. The deletion task could be automated within the Bash script above. Since the Cron timer is only set for once a week, disk usage is probably not a large concern. There are many configuration options to consider.
## Next Steps
diff --git a/docs/websites/cms/turbocharge-wordpress-search-with-solr.md b/docs/websites/cms/turbocharge-wordpress-search-with-solr.md
index 4f675daf35e..c2bda029ce5 100644
--- a/docs/websites/cms/turbocharge-wordpress-search-with-solr.md
+++ b/docs/websites/cms/turbocharge-wordpress-search-with-solr.md
@@ -28,7 +28,7 @@ This guide is written for a non-root user. Commands that require elevated privil
- WordPress must be already installed and configured. If you have not yet installed WordPress, follow the [Manage Web Content with WordPress](/docs/websites/cms/manage-web-content-with-wordpress) guide.
-- Much of this guide assumes that Solr is being installed on the same server as WordPress; however, Solr can be installed on a second server for security or scalibility reasons. Alternate steps are provided should Solr be installed on a second server.
+- Much of this guide assumes that Solr is being installed on the same server as WordPress; however, Solr can be installed on a second server for security or scalability reasons. Alternate steps are provided should Solr be installed on a second server.
## Install Java
@@ -418,7 +418,7 @@ If it shows similar output, Solr is installed and configured correctly:
If Solr is installed on a different server from WordPress, repeat the test from the WordPress server by sending a request to the Solr server:
- curl http://HOSTNAME-OR-IP-OF-SOLR-SERVER:8983/solr/collection1/select
+ curl http://HOSTNAME-OR-IP-OF-SOLR-SERVER:8983/solr/collection1/select
## Install and Configure WPSolr
diff --git a/docs/websites/ecommerce/how-to-install-prestashop-on-ubuntu-16-04.md b/docs/websites/ecommerce/how-to-install-prestashop-on-ubuntu-16-04.md
index 0882b4c6ed3..9521dca309e 100644
--- a/docs/websites/ecommerce/how-to-install-prestashop-on-ubuntu-16-04.md
+++ b/docs/websites/ecommerce/how-to-install-prestashop-on-ubuntu-16-04.md
@@ -236,7 +236,7 @@ You can also use:
-2. Go back to the left menu, and as your mouse pointer hovers on top of **Shop Parameters** you'll see a submenu pop up. Click on **Traffic and SEO**. Scroll down until you find the settings picured below:
+2. Go back to the left menu, and as your mouse pointer hovers on top of **Shop Parameters** you'll see a submenu pop up. Click on **Traffic and SEO**. Scroll down until you find the settings pictured below:
diff --git a/docs/websites/forums/install-and-run-askbot-on-ubuntu-16-04.md b/docs/websites/forums/install-and-run-askbot-on-ubuntu-16-04.md
index 81b58573b7c..6d15bbe7818 100644
--- a/docs/websites/forums/install-and-run-askbot-on-ubuntu-16-04.md
+++ b/docs/websites/forums/install-and-run-askbot-on-ubuntu-16-04.md
@@ -25,7 +25,7 @@ external_resources:
[AskBot](https://askbot.com) is an open-source question-and-answer forum written in Django and Python. It provides features similar to StackOverflow, including a karma-based system, voting, and content moderation. It is used by many popular open source communities such as Ask-FedoraProject and Ask-OpenStack.
-In this guide, you'll install AskBot and deploy with **Nginx** as a web server, **MySQL** as a database server, **Gunicorn** as a Python WSGI HTTP Server and **LetsEncrypt** as a free SSL certificates provider on your Ubuntu 16.04 Linode.
+In this guide, you'll install AskBot and deploy with **NGINX** as a web server, **MySQL** as a database server, **Gunicorn** as a Python WSGI HTTP Server and **LetsEncrypt** as a free SSL certificates provider on your Ubuntu 16.04 Linode.
## Before You Begin
@@ -45,7 +45,7 @@ Throughout this guide, replace `example_user` with a non-root user with `sudo` a
## Install Dependencies and Create a Database
-1. Install the required packages, including Nginx, MySQL, Python PIP, and LetsEncrypt:
+1. Install the required packages, including NGINX, MySQL, Python PIP, and LetsEncrypt:
sudo apt-get install -y python-pip python-dev nginx mysql-server libmysqlclient-dev letsencrypt
@@ -162,7 +162,7 @@ WantedBy=multi-user.target
sudo systemctl start gunicorn
sudo systemctl enable gunicorn
-4. Restart nginx and reload the daemon:
+4. Restart NGINX and reload the daemon:
sudo systemctl daemon-reload
sudo systemctl restart nginx
@@ -171,11 +171,11 @@ WantedBy=multi-user.target
sudo letsencrypt certonly -a webroot --agree-tos --email admin@example.com --webroot-path=/var/www/html -d example.com -d www.example.com
-6. Remove the default Nginx Server Blocks (Virtual Host) and the default Nginix index file to add new AskBot server blocks:
+6. Remove the default NGINX Server Blocks (Virtual Host) and the default NGINX index file to add new AskBot server blocks:
sudo rm -rf /etc/nginx/sites-available/default /etc/nginx/sites-enabled/default /var/www/html/index.nginx-debian.html
-7. Add new `askbot` Nginx Server Blocks (Virtual Host) to run AskBot in the production environment:
+7. Add new `askbot` NGINX Server Blocks (Virtual Host) to run AskBot in the production environment:
{{< file-excerpt "/etc/nginx/sites-available/askbot" conf >}}
server {
@@ -188,12 +188,12 @@ server {
listen 443;
server_name example.com www.example.com;
- ssl on;
+ ssl on;
ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
- location ~ /.well-known {
+ location ~ /.well-known {
allow all;
root /var/www/html;
}
@@ -216,16 +216,16 @@ server {
{{< /file-excerpt >}}
-8. Add a symbolic link between nginx server blocks:
+8. Add a symbolic link between NGINX server blocks:
sudo ln -s /etc/nginx/sites-available/askbot /etc/nginx/sites-enabled
-9. The **www-data** group must have access to AskBot installation directory so that nginx can serve static files, media files, and access the socket files. Add the `example_user` to **www-data** group so that it has the necessary permissions:
+9. The **www-data** group must have access to AskBot installation directory so that NGINX can serve static files, media files, and access the socket files. Add the `example_user` to **www-data** group so that it has the necessary permissions:
sudo usermod -aG www-data example_user
-10. Restart nginx so that the changes take effect:
+10. Restart NGINX so that the changes take effect:
sudo systemctl restart nginx