added host names to dictionary; spelling fixes

ci/vale/dictionary.txt

@@ -86,6 +86,7 @@ bitbucket
 bitrate
 blocklists
 blockwise
+bluehost
 boonex
 bootable
 bootloader
@@ -383,6 +384,7 @@ fstab
 galera
 gamemode
 gameplay
+gandi
 gcc
 gcm
 geckodriver
@@ -494,6 +496,7 @@ hypervisor
 hypervisors
 i386
 iaas
+icann
 icanhazip
 iceweasel
 icinga
@@ -773,6 +776,7 @@ mytestdb
 myuser
 nagios
 nagiosadmin
+namecheap
 nameserver
 nameservers
 namespace

docs/networking/dns/use-linode-name-servers/index.md

@@ -23,7 +23,7 @@ When changing servers, however, you want a shorter TTL to make sure that when yo
 
     {{< image src="whois-icann-name-servers.png" alt="linode.com nameservers" title="whois.icann.org lookup of nameservers for linode.com" >}}
 
-    You can usually derive the website of your nameserver authority (the organization that manages your DNS) from the nameservers you find in the Whois report (e.g. `ns1.linode.com` corresponds with linode.com). Sometimes the labelling for the nameservers is not directly related to the organization's website, and in those cases you can often find the website by plugging the nameserver into a Google search.
+    You can usually derive the website of your nameserver authority (the organization that manages your DNS) from the nameservers you find in the Whois report (e.g. `ns1.linode.com` corresponds with linode.com). Sometimes the labeling for the nameservers is not directly related to the organization's website, and in those cases you can often find the website by plugging the nameserver into a Google search.
 
 1.  Contact your nameserver authority for details on how to shorten the TTL for your domain. Every provider is a little different, so you may have to ask for instructions.
 
@@ -93,4 +93,4 @@ The following support documents describe how to update the authoritative nameser
 
     {{< note >}}
 If you're having trouble seeing your site at the new IP address, you may need to try visiting it in a different browser, or in a private browsing session. Sometimes your browser will cache old DNS data, even if it has updated everywhere else.
-{{< /note >}}
+{{< /note >}}

docs/platform/migrate-to-linode/best-practices-when-migrating-to-linode/index.md

@@ -5,48 +5,48 @@ author:
 description: 'Best practices when migrating a website or other cloud service to Linode.'
 keywords: ["migrate", "website migration"]
 license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
-modified: 2018-07-19
+modified: 2018-07-31
 modified_by:
   name: Linode
-published: 2018-07-19
+published: 2018-07-31
 title: Best Practices when Migrating to Linode
 ---
 
-This guide describes the recommended strategy for migrating your services from another host to Linode. The specific steps you'll need to carry out will vary depending on the software you use, but the high-level outline is generally the same regardless of the nature of your service. The [Migrate to Linode](/docs/platform/migrate-to-linode) section offers other guides which describe migrating particular services in more detail.
+This guide describes the recommended strategy for migrating your services from another host to Linode. The specific steps you'll need to carry out will vary depending on the software you use, but the high-level outline is generally the same regardless of the nature of your service. The [Migrate to Linode](/docs/platform/migrate-to-linode/) section offers other guides which describe migrating particular services in more detail.
 
 ## Deciding on a Migration Strategy
 
 There are two general strategies for migrating from another hosting provider:
 
-1. **Full Clone (Not Recommended)**
+1.  **Install Each Service Individually - Recommended Method**
 
-    -   Create a Linode and perform a full clone of your disks to it from your current host. This will create an exact copy of your disks on the Linode platform. This strategy is not recommended because low-level system configuration files can be different on different hosting providers.
+    -  Create a Linode, deploy a Linode-provided Linux image to it, and copy over only the configuration and data relevant to your services. This results in a Linux environment that is guaranteed to boot normally on the Linode platform.
 
-        These differences can prevent your Linode from booting normally. It is possible to adjust these settings sufficiently to allow your Linode to run normally, but getting the right values for these settings can be difficult, and it can be difficult to troubleshoot when they are incorrect.
+        Re-installing your services can take time, but any issues that come up when setting up your applications are usually easier to troubleshoot than low-level configuration problems. This is the recommended strategy when migrating.
 
-1. **Install Each Service Individually (Recommended)**
+1.  **Full Clone - Not Recommended**
 
-    -   Create a Linode, deploy a Linode-provided Linux image to it, and then copy over only the configuration and data relevant to your services. This will result in a Linux environment that is guaranteed to boot normally on the Linode platform.
+    -  Create a Linode and perform a full clone of your existing disks from your current host to the Linode. This will create an exact copy of your disks on the Linode platform. This strategy is not recommended because low-level system configuration files can be different on different hosting providers.
 
-        The act of re-installing your services can take time, but any issues that come up when setting up your applications are usually easier to troubleshoot than low-level configuration problems. This is the recommended strategy when migrating.
+        These differences can prevent your Linode from booting normally. It is possible to adjust these settings sufficiently to allow your Linode to run normally, but getting the right values for these settings can be difficult, and it can be difficult to troubleshoot when they are incorrect.
 
 ## Migration Strategy Outline
 
 ### Deploy a New Linode
 
 There are two considerations when creating a new Linode: which data center the Linode should reside in, and which hardware resource plan the Linode should run under.
 
-1. **Data Center Location**
+1.  **Data Center Location**
 
-    -   To choose a data center location, run speed tests to the different regions that Linode offers from the [speedtest page](https://www.linode.com/speedtest). This page allows you to download a 100MB file from each location. You can compare the speed of each download to determine the bandwidth between your location and the data center.
+    -  To choose a data center location, run speed tests to the different regions that Linode offers from the [speedtest page](/speedtest/). This page allows you to download a 100MB file from each location. You can compare the speed of each download to determine the bandwidth between your location and the data center.
 
         You can also run [MTR tests](/docs/networking/diagnostics/diagnosing-network-issues-with-mtr/) to the speed test servers at each location (e.g. `speedtest.dallas.linode.com`). These tests will report latency between your location and the data center--a lower latency is more desirable.
 
-1. **Plan Size**
+1.  **Plan Size**
 
-    -   To determine which plan to choose, review the [Linode Pricing page](https://www.linode.com/pricing#all). At a minimum, you should choose a plan which offers enough storage capacity for the data you store on your current hosting provider.
+    -  To determine which plan to choose, review the [Linode Pricing page](/pricing#all). At a minimum, choose a plan which offers enough storage capacity for the data you store on your current hosting provider.
 
-        The CPU and RAM allocations are also important, since a service with a higher workload/higher traffic will require more of each. If you're not sure what your workload will require, you can always start with a smaller Linode and then [resize your plan](docs/platform/disk-images/resizing-a-linode/) upwards or downwards as needed.
+        The CPU and RAM allocations are also important, since a service with a higher workload/higher traffic will require more of each. If you're not sure what your workload will require, you can always start with a smaller Linode and then [resize your plan](/docs/platform/disk-images/resizing-a-linode/) up or down as needed.
 
 ### Deploy Linux
 
@@ -58,33 +58,31 @@ For further details on deploying your new Linux image, follow the [Getting Start
 
 ### Install Software
 
-Install the software stack that is present on your current host on your new Linode. For guidance on how to set up different kinds of software, review Linode's [Guides & Tutorials](/docs/).
+Install the same software stack that is present on your current host on your new Linode. For guidance on how to set up different kinds of software, review Linode's [Guides & Tutorials](/docs/).
 
-If your host provides a shared environment and you're not sure which software is needed, ask your host if they can provide more information about the software they run. For example, WordPress sites are powered by PHP, a web server, and a database, so installing a [LAMP stack](/docs/web-servers/lamp/install-lamp-stack-on-ubuntu-18-04/) would be sufficient.
+If your host provides a shared environment and you're not sure which software is needed, ask your host if they can provide more information about the software they run. For example, WordPress sites are powered by PHP, a web server, and a database, so installing a [LAMP stack](/docs/web-servers/lamp/) would be sufficient.
 
 {{< note >}}
-
-You may want to install your software via a [configuration management tool](https://www.linode.com/docs/applications/configuration-management/). Configuration management is a method for condensing your installation scripts into a *recipe* that can be run repeatedly and which will result in the same deployment every time. Once you've written your recipes, configuration management can greatly speed up creating new deployments and maintenance of existing deployments. These tools also minimize the potential for human error.
-
+You may want to install your software via a [configuration management tool](/docs/applications/configuration-management/). Configuration management is a method for condensing your installation scripts into a *recipe* that can be run repeatedly and which will result in the same deployment every time. Once you've written your recipes, configuration management can greatly speed up creating new deployments and maintenance of existing deployments. These tools also minimize the potential for human error.
 {{< /note >}}
 
 ### Backup Your Data
 
 Locate and backup your data on your current host. You should identify:
 
-- Which software configuration settings should be preserved (e.g. web server, virtual host information, database connection settings, and which files contain these settings, etc).
+- Which software configuration settings should be preserved (e.g. web server, virtual host information, database connection settings, and which files contain these settings, etc.).
 
-- Where your data is stored on disk (e.g. as files in a directory, in a database process, etc).
+- Where your data is stored on disk (e.g. as files in a directory, in a database process, etc.).
 
 If your data is stored in a database, you will likely need to perform a *database dump*. This will result in a file on disk that encapsulates your database data and can be copied over the network as a normal file:
 
--   [Use mysqldump to Back Up MySQL or MariaDB](/docs/databases/mysql/use-mysqldump-to-back-up-mysql-or-mariadb/)
--   [Create Physical Backups of your MariaDB or MySQL Databases](/docs/databases/mysql/create-physical-backups-of-your-mariadb-or-mysql-databases/)
--   [How to Back Up Your PostgreSQL Database](/docs/databases/postgresql/how-to-back-up-your-postgresql-database/)
+-  [Use mysqldump to Back Up MySQL or MariaDB](/docs/databases/mysql/use-mysqldump-to-back-up-mysql-or-mariadb/)
+-  [Create Physical Backups of your MariaDB or MySQL Databases](/docs/databases/mysql/create-physical-backups-of-your-mariadb-or-mysql-databases/)
+-  [How to Back Up Your PostgreSQL Database](/docs/databases/postgresql/how-to-back-up-your-postgresql-database/)
 
 If your current host is a shared environment and you do not have full administrative/command-line access to it, then your host may offer an alternative method for exporting your data. If this is the case, then you should use those tools to download the data to your local computer or some other accessible location.
 
-### Transfer Your Data to Your Linode
+### Use rsync to Transfer Your Data to Your Linode
 
 - Transfer your data to your Linode using a network transfer tool like `rsync`. The [Introduction to rsync](/docs/tools-reference/tools/introduction-to-rsync/) guide is a good place to start to become more familiar with this tool.
 
@@ -93,16 +91,16 @@ If your current host is a shared environment and you do not have full administra
         rsync -avzh /path/to/source_folder example_user@linode_ip_address:/path/to/destination_folder
 
     {{< note >}}
-        `example_user` should be your Linux user on your Linode, and `linode_ip_address` should be your Linode's IP address.
-    {{< /note >}}
+Replace `example_user` with the Linux user on your Linode, and `linode_ip_address` with your Linode's IP address.
+{{< /note >}}
 
 - If your current host is a shared environment and you previously downloaded your data to your computer, then you should upload the data from your computer to your Linode. You can use an SFTP tool like [FileZilla](/docs/tools-reference/file-transfer/filezilla/) to do this, which has clients available for Windows, Mac, and Linux.
 
 - If you have uploaded a database dump file to your new Linode, you will also need to *restore* the dump file so that your database software can use the data normally. The database guides linked to in the [Backup Your Data](#backup-your-data) section include instructions for restoring those files.
 
 ### Test the New Environment
 
-When you have finished setting up your software and restoring your data, you should test the installation to make sure it works normally. At this point, you have not yet updated DNS records to point to your Linode deployment, but there are still methods for [previewing your services](/docs/networking/dns/previewing-websites-without-dns/) without DNS.
+When you have finished setting up your software and restoring your data, you should test the installation to make sure it works normally. At this point, you have not yet updated DNS records to point to your Linode deployment, but there are still methods for [previewing your services without DNS](/docs/networking/dns/previewing-websites-without-dns/).
 
 You can also take this time to perform load testing on your new service. [ApacheBench](https://en.wikipedia.org/wiki/ApacheBench) is a popular benchmarking tool for web services. If you discover that the hardware resource plan you chose originally is not enough when completing these load tests, then you can resize your plan and continue testing.
 
@@ -112,7 +110,7 @@ When you have finished testing, you can move on to the last step in migrating: u
 
 To direct your service visitors to Linode, you will need to associate your domain with [your new Linode's IP](/docs/networking/remote-access/#network-access). There are two options for moving your DNS records:
 
--   Use Linode's [fast, stable DNS hosting](https://www.linode.com/dns-manager) that is free as long as you have one active Linode on your account.
+-   Use Linode's [fast, stable DNS hosting](/dns-manager/) that is free as long as you have one active Linode on your account.
 
 -   Continue to use your current nameserver authority and update your DNS records with your new Linode's IP address. You should check with your current provider to see if there are any costs for their DNS services. If you are using your domain name registrar's nameservers, then they are generally free.
 
@@ -123,23 +121,21 @@ To direct your service visitors to Linode, you will need to associate your domai
 If you'd like to continue with your current nameservers, then you should update all of the DNS records that are assigned to your old host's IP address to use your new Linode's IP. Contact your nameserver authority for instructions on updating your DNS records.
 
 {{< disclosure-note "Updating DNS records at common nameserver authorities" >}}
-
 The following support documents describe how to update DNS records at common nameserver authorities:
 
 -   [GoDaddy](https://www.godaddy.com/help/manage-dns-zone-files-680)
--   [DreamHost](https://help.dreamhost.com/hc/en-us/articles/215414867-How-do-I-add-custom-DNS-records-)
+-   [DreamHost](https://help.dreamhost.com/hc/en-us/articles/215414867-How-do-I-add-custom-DNS-records)
 -   [Gandi](https://doc.gandi.net/en/dns/zone)
--   [1&1](https://www.1and1.com/help/domains/configuring-your-ip-address/connecting-a-domain-to-a-static-ip-address/?utm_campaign=390&utm_content=direct&utm_medium=landinghub&utm_source=helpcenter&utm_term=408)
+-   [1&1](https://www.1and1.com/help/domains/configuring-your-ip-address/connecting-a-domain-to-a-static-ip-address/)
 -   [Network Solutions](http://www.networksolutions.com/support/how-to-manage-advanced-dns-records/)
 -   [Bluehost](https://my.bluehost.com/hosting/help/559)
 -   [HostGator](https://support.hostgator.com/articles/manage-dns-records-with-hostgatorenom)
 -   [Namecheap](https://www.namecheap.com/support/knowledgebase/article.aspx/319/2237/how-can-i-set-up-an-a-address-record-for-my-domain)
 -   [Hover](https://help.hover.com/hc/en-us/articles/217282457-How-to-Edit-DNS-records-A-AAAA-CNAME-MX-TXT-SRV-)
-
 {{< /disclosure-note >}}
 
 After DNS propagation has finished, [set reverse DNS](/docs/networking/dns/configure-your-linode-for-reverse-dns/) for your domain; this is especially important if you are running a mail server.
 
 ## Next Steps
 
-After completing this outline, your service should be fully migrated to Linode. It is a good idea to wait a few days before cancelling your shared hosting service to make sure that everything is running smoothly, and you don't need to obtain more files from your shared host.
+After completing this outline, your service should be fully migrated to Linode. It is a good idea to wait a few days before cancelling your shared hosting service to make sure that everything is running smoothly, and you don't need to obtain more files from your shared host.

docs/platform/migrate-to-linode/migrate-a-lamp-website-to-linode/index.md

@@ -77,7 +77,7 @@ If any new information is added to the database on the current host prior to ful
 
 ### Transfer Data to Linode
 
-The following commands will copy files into the home directory of your Linode's Linux user. The next section will ensure that these files are moved to the right locations on disk and that their file owneship is correct. This work is done in two steps because the Linux user is assumed to have limited privileges and is unable to write to certain locations on disk.
+The following commands will copy files into the home directory of your Linode's Linux user. The next section will ensure that these files are moved to the right locations on disk and that their file ownership is correct. This work is done in two steps because the Linux user is assumed to have limited privileges and is unable to write to certain locations on disk.
 
 1.  From your current host, upload the Apache configuration files to your new Linode:
 
@@ -148,4 +148,4 @@ If you are seeing any other errors from your site, try reviewing Apache's error
 
 The last step required to migrate is to update your DNS records to reflect your new Linode's IP. Once this is done, visitors will start loading the page from your Linode.
 
-{{< content "use-linode-name-servers" >}}
+{{< content "use-linode-name-servers" >}}