From 50100ab8e831d25fa6baa2e6eb9b3e9c93539279 Mon Sep 17 00:00:00 2001
From: "Jose J. Escobar" <53836904+jescobar-docker@users.noreply.github.com>
Date: Wed, 2 Oct 2019 07:36:05 -0400
Subject: [PATCH] Update upgrade.md (#9548)

Fixed typo.
I think I fixed broken link. Same link was working just below the fixed one. I copied text from there.
---
 ee/ucp/interlock/deploy/upgrade.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/ee/ucp/interlock/deploy/upgrade.md b/ee/ucp/interlock/deploy/upgrade.md
index 19f2c514d6..e695a0247e 100644
--- a/ee/ucp/interlock/deploy/upgrade.md
+++ b/ee/ucp/interlock/deploy/upgrade.md
@@ -33,7 +33,7 @@ deployed. As part of this, services using HRM labels are inspected.
 3. The HRM service is removed.
 4. The `ucp-interlock` service is deployed with the configuration created.
 5. The `ucp-interlock` service deploys the `ucp-interlock-extension` and
-`ucp-interlock-proxy-services`.
+`ucp-interlock-proxy` services.
 
 The only way to rollback from an upgrade is by restoring from a backup taken
 before the upgrade. If something goes wrong during the upgrade process, you
@@ -90,7 +90,7 @@ don't have any configuration with the same name by running:
 * If either the `ucp-interlock-extension` or `ucp-interlock-proxy` services are
 not running, it's possible that there are port conflicts.
 As a workaround re-enable the layer 7 routing configuration from the
-[UCP settings page](deploy/index.md). Make sure the ports you choose are not
+[UCP settings page](index.md). Make sure the ports you choose are not
 being used by other services.
 
 ## Workarounds and clean-up