From 19dbe8d58448db6fa40d1866bac51bf47429fe26 Mon Sep 17 00:00:00 2001
From: erganzi <41982810+erganzi@users.noreply.github.com>
Date: Wed, 31 Oct 2018 01:05:08 +0800
Subject: [PATCH] Update ingress.md (#10752)

Fix a small mistake
---
 content/en/docs/tasks/administer-federation/ingress.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/tasks/administer-federation/ingress.md b/content/en/docs/tasks/administer-federation/ingress.md
index d2f70cd6d5..51bfce65d5 100644
--- a/content/en/docs/tasks/administer-federation/ingress.md
+++ b/content/en/docs/tasks/administer-federation/ingress.md
@@ -85,7 +85,7 @@ You can create a federated ingress in any of the usual ways, for example, using
 kubectl --context=federation-cluster create -f myingress.yaml
 ```
 For example ingress YAML configurations, see the [Ingress User Guide](/docs/concepts/services-networking/ingress/).
-The '--context=federation-cluster' flag tells kubectl to submit the
+The `--context=federation-cluster` flag tells kubectl to submit the
 request to the Federation API endpoint, with the appropriate
 credentials. If you have not yet configured such a context, see the
 [federation admin guide](/docs/admin/federation/) or one of the