From 2d9d9dbe7a62620329844459a79e30dc1e8ae2a1 Mon Sep 17 00:00:00 2001 From: trujillo-adam Date: Wed, 23 Jun 2021 08:50:30 -0700 Subject: [PATCH] docs: fixed instance of incorrect grammar usage --- .../content/docs/upgrading/instructions/upgrade-to-1-10-x.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/content/docs/upgrading/instructions/upgrade-to-1-10-x.mdx b/website/content/docs/upgrading/instructions/upgrade-to-1-10-x.mdx index e07df04677..c0d261a141 100644 --- a/website/content/docs/upgrading/instructions/upgrade-to-1-10-x.mdx +++ b/website/content/docs/upgrading/instructions/upgrade-to-1-10-x.mdx @@ -13,11 +13,11 @@ description: >- ## Introduction This guide explains how to best upgrade a single Consul Enterprise datacenter to v1.10.0 -from a version of Consul that is forwards compatible with v1.10. If you are on a major +from a version of Consul that is forward compatible with v1.10. If you are on a major version of Consul prior to 1.8, you will need to complete and [upgrade to 1.8.13](/docs/upgrading/instructions) or higher before continuing with this guide. If you are already on a major version of 1.8 or 1.9, then this guide will go over the procedures required for upgrading to v1.10. This process -will require intermediate version upgrades to a forward compatible release of v1.8 or v1.9, +will require intermediate version upgrades to a forward-compatible release of v1.8 or v1.9, as well as other licensing related configuration changes. If you have multiple Consul datacenters, upgrade them in the normal order and take the following instructions into account for each upgrade.