This is an automated email from the ASF dual-hosted git repository.
membphis pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/apisix.git
The following commit(s) were added to refs/heads/master by this push:
new e5cd46e docs: fix grammar (#3539)
e5cd46e is described below
commit e5cd46e38e09d1025817381a3bf0b85a4f02a528
Author: John Bampton <jbamp...@users.noreply.github.com>
AuthorDate: Sun Feb 7 00:55:48 2021 +1000
docs: fix grammar (#3539)
---
apisix/plugins/tcp-logger.lua | 2 +-
doc/architecture-design.md | 2 +-
doc/plugins/authz-keycloak.md | 2 +-
doc/plugins/echo.md | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/apisix/plugins/tcp-logger.lua b/apisix/plugins/tcp-logger.lua
index 66e8e2f..dc4cb21 100644
--- a/apisix/plugins/tcp-logger.lua
+++ b/apisix/plugins/tcp-logger.lua
@@ -79,7 +79,7 @@ local function send_tcp_data(conf, log_message)
if conf.tls then
ok, err = sock:sslhandshake(true, conf.tls_options, false)
if not ok then
- return false, "failed to to perform TLS handshake to TCP server:
host["
+ return false, "failed to perform TLS handshake to TCP server:
host["
.. conf.host .. "] port[" .. tostring(conf.port) ..
"] err: " .. err
end
end
diff --git a/doc/architecture-design.md b/doc/architecture-design.md
index 1edc311..fca94b1 100644
--- a/doc/architecture-design.md
+++ b/doc/architecture-design.md
@@ -81,7 +81,7 @@ The following image shows an example of some Route rules.
When some attribute va
<img src="./images/routes-example.png" width="50%" height="50%">
-We configure all the parameters directly in the Route, it's easy to set up,
and each Route has a relatively high degree of freedom. But when our Route has
more repetitive configurations (such as enabling the same plugin configuration
or upstream information), once we need update these same properties, we have to
traverse all the Routes and modify them, so it adding a lot of complexity of
management and maintenance.
+We configure all the parameters directly in the Route, it's easy to set up,
and each Route has a relatively high degree of freedom. But when our Route has
more repetitive configurations (such as enabling the same plugin configuration
or upstream information), once we need update these same properties, we have to
traverse all the Routes and modify them, so it's adding a lot of complexity of
management and maintenance.
The shortcomings mentioned above are independently abstracted in APISIX by the
two concepts [Service](#service) and [Upstream](#upstream).
diff --git a/doc/plugins/authz-keycloak.md b/doc/plugins/authz-keycloak.md
index f2979c7..415e313 100644
--- a/doc/plugins/authz-keycloak.md
+++ b/doc/plugins/authz-keycloak.md
@@ -31,7 +31,7 @@
## Name
`authz-keycloak` is an authorization plugin to be used with the Keycloak
Identity Server. Keycloak is an OAuth/OIDC and
-UMA compliant Identity Server. Although, its developed to working in
conjunction with Keycloak it should work with any
+UMA compliant Identity Server. Although, it's developed working in conjunction
with Keycloak it should work with any
OAuth/OIDC and UMA compliant identity providers as well.
For more information on Keycloak, refer to [Keycloak Authorization
Docs](https://www.keycloak.org/docs/latest/authorization_services) for more
information.
diff --git a/doc/plugins/echo.md b/doc/plugins/echo.md
index 2430cbf..118671a 100644
--- a/doc/plugins/echo.md
+++ b/doc/plugins/echo.md
@@ -29,7 +29,7 @@
## Name
-`echo` is a a useful plugin to help users understand as fully as possible how
to develop an APISIX plugin.
+`echo` is a useful plugin to help users understand as fully as possible how to
develop an APISIX plugin.
This plugin addresses the corresponding functionality in the common phases
such as init, rewrite, access, balancer, header filer, body filter and log.
