You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@apisix.apache.org by kv...@apache.org on 2021/07/10 14:54:45 UTC

[apisix-ingress-controller] 01/01: fix: misspell

This is an automated email from the ASF dual-hosted git repository.

kvn pushed a commit to branch v1.1.0
in repository https://gitbox.apache.org/repos/asf/apisix-ingress-controller.git

commit ac7227f58fe96dcad7d086b1ddaebead195433f9
Author: kv <gx...@163.com>
AuthorDate: Sat Jul 10 22:54:17 2021 +0800

    fix: misspell
---
 docs/en/latest/FAQ.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/en/latest/FAQ.md b/docs/en/latest/FAQ.md
index 8786def..7c92f9a 100644
--- a/docs/en/latest/FAQ.md
+++ b/docs/en/latest/FAQ.md
@@ -49,7 +49,7 @@ Tips: The failure caused by empty upstream nodes is a limitation of Apache APISI
 
 6. What is the retry rule of `apisix-ingress-controller`?
 
-If an error occurs duriREADME.mdng the process of `apisix-ingress-controller` parsing CRD and distributing the configuration to APISIX, a retry will be triggered.
+If an error occurs during the process of `apisix-ingress-controller` parsing CRD and distributing the configuration to APISIX, a retry will be triggered.
 
 The delayed retry method is adopted. After the first failure, it is retried once per second. After 5 retries are triggered, the slow retry strategy will be enabled, and the retry will be performed every 1 minute until it succeeds.