[skywalking] branch kezhenxu94-patch-1 created (now 57b6361)

[ke...@apache.org]

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

kezhenxu94 pushed a change to branch kezhenxu94-patch-1
in repository https://gitbox.apache.org/repos/asf/skywalking.git.


      at 57b6361  Update als_setting.md

This branch includes the following new commits:

     new 57b6361  Update als_setting.md

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.

[skywalking] 01/01: Update als_setting.md

[ke...@apache.org]

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

kezhenxu94 pushed a commit to branch kezhenxu94-patch-1
in repository https://gitbox.apache.org/repos/asf/skywalking.git

commit 57b6361b2491d8254a38ba2e3c8a6ffbff266a84
Author: kezhenxu94 <ke...@apache.org>
AuthorDate: Fri Sep 25 23:39:59 2020 +0800

    Update als_setting.md
---
 docs/en/setup/envoy/als_setting.md | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/docs/en/setup/envoy/als_setting.md b/docs/en/setup/envoy/als_setting.md
index 02eb622..5c02dbd 100644
--- a/docs/en/setup/envoy/als_setting.md
+++ b/docs/en/setup/envoy/als_setting.md
@@ -1,8 +1,8 @@
 # Observe service mesh through ALS
 Envoy [ALS(access log service)](https://www.envoyproxy.io/docs/envoy/latest/api-v2/service/accesslog/v2/als.proto) provides
-fully logs about RPC routed, including HTTP and TCP.
+full logs about RPC routed, including HTTP and TCP.
 
-If solution initialized and first implemented by [Sheng Wu](https://github.com/wu-sheng), [Hongtao Gao](https://github.com/hanahmily), [Lizan Zhou](https://github.com/lizan), 
+The solution is initialized and firstly implemented by [Sheng Wu](https://github.com/wu-sheng), [Hongtao Gao](https://github.com/hanahmily), [Lizan Zhou](https://github.com/lizan), 
 and [Dhi Aurrahman](https://github.com/dio) at 17 May. 2019, 
 and presented on [KubeCon China 2019](https://kccncosschn19eng.sched.com/event/NroB/observability-in-service-mesh-powered-by-envoy-and-apache-skywalking-sheng-wu-lizan-zhou-tetrate).
 Here is the recorded [Video](https://www.youtube.com/watch?v=tERm39ju9ew).
@@ -16,7 +16,7 @@ You need three steps to open ALS.
     ```
     istioctl manifest apply --set profile=demo --set meshConfig.defaultConfig.envoyAccessLogService.address=skywalking-oap.skywalking.svc:11800 --set meshConfig.enableEnvoyAccessLogService=true
     ```
-    Note:Skywalking oap service is at skywalking namespace, and the port of gRPC service is 11800
+    Note: SkyWalking OAP service is at skywalking namespace, and the port of gRPC service is 11800
     
 2. (Default is ACTIVATED) Activate SkyWalking [envoy receiver](../backend/backend-receivers.md). 
 3. Active ALS k8s-mesh analysis, set system env variable `SW_ENVOY_METRIC_ALS_HTTP_ANALYSIS`=`k8s-mesh`
@@ -27,14 +27,14 @@ envoy-metric:
     acceptMetricsService: ${SW_ENVOY_METRIC_SERVICE:true}
     alsHTTPAnalysis: ${SW_ENVOY_METRIC_ALS_HTTP_ANALYSIS:""} # Setting the system env variable would override this. 
 ```
-Note multiple value，please use `,` symbol split
+For multiple values，please use `,` symbol to concatenate.
 
 Here's an example to deploy SkyWalking by Helm chart.
 
 ```
 istioctl install --set profile=demo --set meshConfig.defaultConfig.envoyAccessLogService.address=skywalking-oap.istio-system:11800 --set meshConfig.enableEnvoyAccessLogService=true
 
-git checkout https://github.com/apache/skywalking-kubernetes.git
+git clone https://github.com/apache/skywalking-kubernetes.git
 cd skywalking-kubernetes/chart
 
 helm repo add elastic https://helm.elastic.co
@@ -44,6 +44,6 @@ helm dep up skywalking
 helm install 8.1.0 skywalking -n istio-system --set oap.env.SW_ENVOY_METRIC_ALS_HTTP_ANALYSIS=k8s-mesh --set fullnameOverride=skywalking --set oap.envoy.als.enabled=true
 ```
 
-Notice, only use this when envoy under Istio controlled, also in k8s env. The OAP requires the read right to k8s API server for all pods IPs.
+Notice, only use this when Envoy is under Istio's control, and they are in k8s environment. The OAP requires the read right to k8s API server for all pods IPs.
 
-You can use `kubectl logs ${You-OAP-Pod} | grep "K8sALSServiceMeshHTTPAnalysis"` to ensure OAP ALS k8s-mesh analysis has been active.
+You can use `kubectl -n istio-system logs -l app=skywalking | grep "K8sALSServiceMeshHTTPAnalysis"` to ensure OAP ALS k8s-mesh analysis has been active.