[echarts-doc] branch master updated: fix(tutorial): correct some typos and broken links.

[wa...@apache.org]

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

wangzx pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/echarts-doc.git


The following commit(s) were added to refs/heads/master by this push:
     new 1c291b6  fix(tutorial): correct some typos and broken links.
     new 19b0fa3  Merge branch 'master' of https://github.com/apache/echarts-doc
1c291b6 is described below

commit 1c291b6efb435dc06edc94e4fcdbb1dae75c1c00
Author: plainheart <yh...@all-my-life.cn>
AuthorDate: Tue Jan 26 17:02:10 2021 +0800

    fix(tutorial): correct some typos and broken links.
---
 en/tutorial/headless.md | 2 +-
 en/tutorial/renderer.md | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/en/tutorial/headless.md b/en/tutorial/headless.md
index 496ce6d..2bae6de 100644
--- a/en/tutorial/headless.md
+++ b/en/tutorial/headless.md
@@ -3,7 +3,7 @@
 
 # Server-side Rendering
 
-Apache ECharts<sup>TM</sup> can be rendered at server-side. For example, the thumbnails in the [official examples page](https://echarts.apache.org/examples/en/index.html/) are generated at a server.
+Apache ECharts<sup>TM</sup> can be rendered at server-side. For example, the thumbnails in the [official examples page](https://echarts.apache.org/examples/en/index.html) are generated at a server.
 
 Commonly used headless tool is required, for example, [puppeteer](https://github.com/GoogleChrome/puppeteer), [headless chrome](https://chromium.googlesource.com/chromium/src/+/lkgr/headless/README.md), [node-canvas](https://github.com/Automattic/node-canvas), [jsdom](https://github.com/jsdom/jsdom), [PhantomJS](http://phantomjs.org/), etc.
 
diff --git a/en/tutorial/renderer.md b/en/tutorial/renderer.md
index 0f93b36..499fe8d 100644
--- a/en/tutorial/renderer.md
+++ b/en/tutorial/renderer.md
@@ -6,7 +6,7 @@ Most of browser-side charting libraries use SVG or Canvas as their underlying re
 
 ECharts has been using Canvas as its renderer (use VML for IE8-) from the beginning. As of [ECharts v3.8](https://github.com/apache/echarts/releases) we provide an SVG renderer (beta version) as another option. Either of them can be used by specifing parameter [renderer](api.html#echarts.init) as `'canvas'` or `'svg'` when initailizing a chart instance.
 
-> Both SVG and Canvas, which are very different rendering implementations, are supported in ECharts by leveraging the Canvas and SVG renderers offered by the [zender](https://github.com/ecomfe/zrender) library.
+> Both SVG and Canvas, which are very different rendering implementations, are supported in ECharts by leveraging the Canvas and SVG renderers offered by the [zrender](https://github.com/ecomfe/zrender) library.
 
 ## How to make a choice?
 
@@ -35,7 +35,7 @@ ECharts uses Canvas by default. If a user intends to use the SVG renderer, the m
 
 + In the [pre-build](https://www.jsdelivr.com/package/npm/echarts) of ECharts, the SVG renderer has been included in [common version](https://cdn.jsdelivr.net/npm/echarts/dist/echarts.common.min.js) and [complete version](https://cdn.jsdelivr.net/npm/echarts/dist/echarts.min.js). But not in [simple version](https://cdn.jsdelivr.net/npm/echarts/dist/echarts.simple.min.js).
 + When [building ECharts online](${websitePath}/en/builder.html), the checkbox "SVG Renderer" should be checked.
-+ When [buildin ECharts offline](tutorial.html#Create%20Custom%20Build%20of%20ECharts), the SVG renderer module should be imported:
++ When [building ECharts offline](tutorial.html#Use%20ECharts%20with%20bundler%20and%20NPM), the SVG renderer module should be imported:
 
 ```js
 import 'zrender/lib/svg/svg';


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@echarts.apache.org
For additional commands, e-mail: commits-help@echarts.apache.org