[skywalking] branch master updated: Is it a typo or not? (#3537)

[wu...@apache.org]

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

wusheng pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/skywalking.git


The following commit(s) were added to refs/heads/master by this push:
     new 9dccace  Is it a typo or not? (#3537)
9dccace is described below

commit 9dccace951787bf7dbfb2c1cd6c6d1b2a0eadfdb
Author: panjuan <pa...@apache.org>
AuthorDate: Fri Sep 27 21:50:00 2019 +0800

    Is it a typo or not? (#3537)
---
 docs/en/setup/backend/backend-receivers.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/en/setup/backend/backend-receivers.md b/docs/en/setup/backend/backend-receivers.md
index 2dbc589..2f8dbbd 100644
--- a/docs/en/setup/backend/backend-receivers.md
+++ b/docs/en/setup/backend/backend-receivers.md
@@ -4,7 +4,7 @@ or tracing data from other being monitored system, are all being called **Receiv
 receivers are using gRPC or HTTPRestful to provide service, actually, whether listening mode or pull mode
 could be receiver. Such as a receiver could base on pull data from remote, like Kakfa MQ.
 
-We have following receivers, and `default` implementors are provided in our Apache distribution.zzz
+We have following receivers, and `default` implementors are provided in our Apache distribution.
 1. **receiver-trace**. gRPC and HTTPRestful services to accept SkyWalking format traces.
 1. **receiver-register**. gRPC and HTTPRestful services to provide service, service instance and endpoint register.
 1. **service-mesh**. gRPC services accept data from inbound mesh probes.