From b28981e7ab81aeee928a1b815e13fd18aa31989e Mon Sep 17 00:00:00 2001
From: JuleeB1 <42522858+JuleeB1@users.noreply.github.com>
Date: Tue, 21 Aug 2018 12:52:58 -0500
Subject: [PATCH] Added Note Formatting (#9986)

Added note tags to the text.
---
 content/en/docs/tasks/administer-federation/hpa.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/content/en/docs/tasks/administer-federation/hpa.md b/content/en/docs/tasks/administer-federation/hpa.md
index 839b4d04d3..f33294cfce 100644
--- a/content/en/docs/tasks/administer-federation/hpa.md
+++ b/content/en/docs/tasks/administer-federation/hpa.md
@@ -122,10 +122,10 @@ in the previous section.
 
 You can delete a federated HPA as you would delete a Kubernetes
 HPA; however, for a federated HPA, you must send the request to
-the federation API server instead of sending it to a specific Kubernetes cluster.
-It should also be noted that for the federated resource to be deleted from
-all underlying clusters, [cascading deletion](/docs/concepts/cluster-administration/federation/#cascading-deletion)
-should be used.
+the federation API server instead of to a specific Kubernetes cluster.
+{{< note >}}
+**Note:** For the federated resource to be deleted from all underlying clusters, [cascading deletion](/docs/concepts/cluster-administration/federation/#cascading-deletion) should be used.
+{{< /note >}}
 
 For example, you can do that using `kubectl` by running: