[skywalking] branch master updated: fix doc_Trace Data Protocol v2_error #2620 (#2625)

[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 ba73d34  fix doc_Trace Data Protocol v2_error #2620 (#2625)
ba73d34 is described below

commit ba73d3420b5e3cd78769957729a2c31e31777a4c
Author: coki230 <xi...@126.com>
AuthorDate: Tue May 7 19:25:57 2019 +0800

    fix doc_Trace Data Protocol v2_error #2620 (#2625)
    
    fix doc_Trace Data Protocol v2_error #2620
---
 docs/en/protocols/Trace-Data-Protocol-v2.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/en/protocols/Trace-Data-Protocol-v2.md b/docs/en/protocols/Trace-Data-Protocol-v2.md
index b574c54..c25f8a1 100644
--- a/docs/en/protocols/Trace-Data-Protocol-v2.md
+++ b/docs/en/protocols/Trace-Data-Protocol-v2.md
@@ -24,7 +24,7 @@ Because batch is supported, even for most language agent/SDK, no scenario to do
 and `UUID` in response, and match with your expected value.
 
 ### Step 2. Send trace and metric
-After you have trace id and trace instance id, you could send traces and metric. Now we
+After you have service id and service instance id, you could send traces and metric. Now we
 have 
 1. `TraceSegmentReportService#collect` for skywalking native trace format
 1. `JVMMetricReportService#collect` for skywalking native jvm format