[skywalking] branch website-docs/8.2.0 updated: Replace doc files URL with`https` on branch website-docs/8.2.0 (#6373)

[wu...@apache.org]

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

wusheng pushed a commit to branch website-docs/8.2.0
in repository https://gitbox.apache.org/repos/asf/skywalking.git


The following commit(s) were added to refs/heads/website-docs/8.2.0 by this push:
     new 73e0d67  Replace doc files URL with`https` on branch website-docs/8.2.0 (#6373)
73e0d67 is described below

commit 73e0d67c0e6deb61408db8ecc9ef163fced4d2ff
Author: Juntao Zhang <jt...@163.com>
AuthorDate: Mon Feb 15 22:05:00 2021 +0800

    Replace doc files URL with`https` on branch website-docs/8.2.0 (#6373)
---
 docs/en/concepts-and-designs/overview.md  |  2 +-
 docs/en/setup/backend/backend-ui-setup.md |  2 +-
 docs/en/ui/README.md                      | 14 +++++++-------
 3 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/docs/en/concepts-and-designs/overview.md b/docs/en/concepts-and-designs/overview.md
index 471041b..3abebb2 100644
--- a/docs/en/concepts-and-designs/overview.md
+++ b/docs/en/concepts-and-designs/overview.md
@@ -30,7 +30,7 @@ In addition, you can integrate
 ## Architecture
 SkyWalking is logically split into four parts: Probes, Platform backend, Storage and UI.
 
-<img src="http://skywalking.apache.org/assets/frame-v8.jpg?u=20200423"/>
+<img src="https://skywalking.apache.org/assets/frame-v8.jpg?u=20200423"/>
 
 - **Probe**s collect data and reformat them for SkyWalking requirements (different probes support different sources).
 - **Platform backend**, supports data aggregation, analysis and drives process flow from probes to the UI. The analysis includes
diff --git a/docs/en/setup/backend/backend-ui-setup.md b/docs/en/setup/backend/backend-ui-setup.md
index b75a2e5..378a84d 100644
--- a/docs/en/setup/backend/backend-ui-setup.md
+++ b/docs/en/setup/backend/backend-ui-setup.md
@@ -37,7 +37,7 @@ In Java, .NetCore, Node.js, Istio agents/probe, you should set the gRPC service
 
 Before deploying Skywalking in your distributed environment, you should know how agents/probes, backend, UI communicates with each other:
 
-<img src="http://skywalking.apache.org/doc-graph/communication-net.png"/>
+<img src="https://skywalking.apache.org/doc-graph/communication-net.png"/>
 
 - All native agents and probes, either language based or mesh probe, are using gRPC service (`core/default/gRPC*` in `application.yml`) to report data to the backend. Also, jetty service supported in JSON format. 
 - UI uses GraphQL (HTTP) query to access the backend also in Jetty service (`core/default/rest*` in `application.yml`).
diff --git a/docs/en/ui/README.md b/docs/en/ui/README.md
index 1096b11..9d14498 100644
--- a/docs/en/ui/README.md
+++ b/docs/en/ui/README.md
@@ -8,7 +8,7 @@ The latest introduction video could be found on the Youtube
 
 SkyWalking dashboard includes the following part.
 
-<img src="http://skywalking.apache.org/ui-doc/7.0.0/dashboard.png"/>
+<img src="https://skywalking.apache.org/ui-doc/7.0.0/dashboard.png"/>
 
 1. **Feature Tab Selector Zone**. The key features are list there. The more details will be introduced below.
 1. **Reload Zone**. Control the reload mechanism, including reload periodically or manually.
@@ -25,11 +25,11 @@ Dashboard provide metrics of service, service instance and endpoint. There are a
 Service, Instance and Dashboard selector could reload manually rather than reload the whole page. NOTICE, the **Reload Zone**
 wouldn't reload these selectors.
 
-<img src="http://skywalking.apache.org/ui-doc/7.0.0/dashboard-reload.png"/>
+<img src="https://skywalking.apache.org/ui-doc/7.0.0/dashboard-reload.png"/>
 
 Two default dashboards are provided to visualize the metrics of service and database.
 
-<img src="http://skywalking.apache.org/ui-doc/7.0.0/dashboard-default.png"/>
+<img src="https://skywalking.apache.org/ui-doc/7.0.0/dashboard-default.png"/>
 
 User could click the `lock` button left aside the `Service/Instance/Endpoint Reload` button to custom your own dashboard.
 
@@ -87,7 +87,7 @@ Check the entity named as `ui_template` in your storage.
 ## Topology
 Topology map shows the relationship among the services and instances with metrics.
 
-<img src="http://skywalking.apache.org/ui-doc/7.0.0/topology.png"/>
+<img src="https://skywalking.apache.org/ui-doc/7.0.0/topology.png"/>
 
 * Topology shows the default global topology including all services.
 * **Service Selector** supports to show direct relationships including upstream and downstream.
@@ -98,7 +98,7 @@ Topology map shows the relationship among the services and instances with metric
 ## Trace Query
 Trace query is a typical feature as SkyWalking provided distributed agents.
 
-<img src="http://skywalking.apache.org/ui-doc/7.0.0/trace.png"/>
+<img src="https://skywalking.apache.org/ui-doc/7.0.0/trace.png"/>
 
 * **Trace Segment List** is not the trace list. Every trace has several segments belonging to different services. If  
 query by all services or by trace id, different segments with same trace id could be list there.
@@ -110,7 +110,7 @@ Profile is an interaction feature. It provides the method level performance diag
 
 To start the profile analysis, user need to create the profile task
 
-<img src="http://skywalking.apache.org/ui-doc/7.0.0/profile-create.png" width="440px"/>
+<img src="https://skywalking.apache.org/ui-doc/7.0.0/profile-create.png" width="440px"/>
 
 1. Select the specific service. 
 1. Set the endpoint name. This endpoint name typically is the operation name of the first span. Find this on the trace 
@@ -133,7 +133,7 @@ Typically, we analysis spans having long self duration, if the span and its chil
 After choose the right span, and click the `analysis` button, you will see the stack based analysis result. The slowest methods
 have been highlighted.
 
-<img src="http://skywalking.apache.org/ui-doc/7.0.0/profile-result.png"/>
+<img src="https://skywalking.apache.org/ui-doc/7.0.0/profile-result.png"/>
 
 ### Advanced features
 1. Since 7.1.0, the profiled trace collects the HTTP request parameters for Tomcat and SpringMVC Controller automatically.