From b63225bcd129a8af1ece16fb618b3a100e1bb070 Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Fri, 7 Sep 2018 16:02:41 -0700 Subject: [PATCH] fixed typo --- content/rancher/v2.x/en/v1.6-migration/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.x/en/v1.6-migration/_index.md b/content/rancher/v2.x/en/v1.6-migration/_index.md index 65ca99338ca..5c0abfb7dac 100644 --- a/content/rancher/v2.x/en/v1.6-migration/_index.md +++ b/content/rancher/v2.x/en/v1.6-migration/_index.md @@ -6,7 +6,7 @@ draft: true Rancher 2.0 has been rearchitected and rewritten with the goal of providing a complete management solution for Kubernetes and Docker. Due to these extensive changes, there is no direct upgrade path from 1.6.x to 2.x, but rather a migration of your 1.6 application workloads into the 2.0 Kubernetes equivalent. In 1.6, the most common orchestration used was Rancher's own engine called Cattle. The following blogs (that will be converted in an official guide) explain and educate our Cattle users on running workloads in a Kubernetes environment. -If you are an existing Kubernetes user on Rancher 1.6, you only need to review the [Get Started](#1-get-started)} section to prepare you on what to expect on a new 2.0 Rancher cluster. +If you are an existing Kubernetes user on Rancher 1.6, you only need to review the [Get Started](#1-get-started) section to prepare you on what to expect on a new 2.0 Rancher cluster. ## Kubernetes Basics