Point to istio/istio master. (#4020)

And fix a broken link to Envoy.

content/boilerplates/notes/0.8.md

@@ -5,7 +5,7 @@
 deployment [use-cases](/docs/tasks/traffic-management/). For folks upgrading from earlier releases there is a
 [migration guide](/docs/setup/kubernetes/upgrade/) and a conversion tool built into `istioctl` to help convert your configuration from the old model.
 
-- **Streaming Envoy configuration**. By default Pilot now streams configuration to Envoy using its [ADS API](https://github.com/envoyproxy/data-plane-api/blob/master/XDS_PROTOCOL.md). This new approach increases effective scalability, reduces rollout delay and should eliminate spurious 404 errors.
+- **Streaming Envoy configuration**. By default Pilot now streams configuration to Envoy using its [ADS API](https://github.com/envoyproxy/data-plane-api/blob/master/xds_protocol.rst). This new approach increases effective scalability, reduces rollout delay and should eliminate spurious 404 errors.
 
 - **Gateway for Ingress/Egress**. We no longer support combining Kubernetes Ingress specs with Istio routing rules as it has led to several bugs and reliability issues. Istio now supports a platform independent [Gateway](/docs/concepts/traffic-management/#gateways) model for ingress & egress proxies that works across Kubernetes and Cloud Foundry and works seamlessly with routing. The Gateway supports [Server Name Indication](https://en.wikipedia.org/wiki/Server_Name_Indication) based routing,
 as well as serving a certificate based on the server name presented by the client.

content/docs/setup/consul/install/index.md

@@ -119,7 +119,7 @@ Part of the sidecar installation should involve setting up appropriate IP
 Table rules to transparently route application's network traffic through
 the Istio sidecars. The IP table script to setup such forwarding can be
 found in the
-[here]({{< github_file >}}/tools/deb/istio-iptables.sh).
+[here]({{< github_file >}}/tools/packaging/common/istio-iptables.sh).
 
 {{< warning >}}
 This script must be executed before starting the application or

content_zh/boilerplates/notes/0.8.md

@@ -2,7 +2,7 @@
 
 - **重构网络管理模型**：[新的流量管理 API](/zh/blog/2018/v1alpha3-routing/) 业已就绪。新的模型覆盖了更多真实世界的部署[用例](/zh/docs/tasks/traffic-management/)，更加易于理解和使用。如果要从早期部署中进行升级，这里提供了[升级指南](/zh/docs/setup/kubernetes/upgrade/)，并且在 `istioctl` 中加入了转换工具，帮助用户对旧版本配置进行升级。
 
-- **Envoy 配置传播**：新版本中，Pilot 缺省使用 Envoy 的 [ADS API](https://github.com/envoyproxy/data-plane-api/blob/master/XDS_PROTOCOL.md) 进行配置传播。这种新方法提高了稳定性、降低了生效延迟，应该也解决了之前的方法造成的 404 错误。
+- **Envoy 配置传播**：新版本中，Pilot 缺省使用 Envoy 的 [ADS API](https://github.com/envoyproxy/data-plane-api/blob/master/xds_protocol.rst) 进行配置传播。这种新方法提高了稳定性、降低了生效延迟，应该也解决了之前的方法造成的 404 错误。
 
 - **Ingress/Egress Gateway**：路由规则不再提供对 Kubernetes Ingress 规范的支持，这种支持曾经导致了大量的 Bug 和可靠性问题。Istio 现在为 Ingress 和 Egress 代理提供了平台独立的 [Gateway](/zh/docs/concepts/traffic-management/#gateway) 模型。新模型能够很好的和 Kubernetes 以及 Cloud Foundry 协作，并可以无缝应用路由能力。Gateway 支持基于 [服务器命名认证（SNI）](https://en.wikipedia.org/wiki/Server_Name_Indication) 的路由功能，并且能够根据客户端要求的服务器名称提供证书。
 

content_zh/docs/setup/consul/install/index.md

@@ -82,7 +82,7 @@ Istio Pilot 、Mixer 和 Citadel 的 Debian 包可以通过 Istio 的发行版
 
 ## 通过 Istio sidecars 做流量路由
 
-为了能够通过 Istio sidecars 透明地路由应用的网络流量，部分 sidecar 的安装需要设置适当的 IP Table 规则。这种转发规则的 IP Table 脚本可以在[这里]({{< github_file >}}/tools/deb/istio-iptables.sh)找到。
+为了能够通过 Istio sidecars 透明地路由应用的网络流量，部分 sidecar 的安装需要设置适当的 IP Table 规则。这种转发规则的 IP Table 脚本可以在[这里]({{< github_file >}}/tools/packaging/common/istio-iptables.sh)找到。
 
 {{< warning >}}
 该脚本必须在启动应用和 sidecar 之前执行。

data/args.yml

@@ -20,7 +20,7 @@ archive_date: YYYY-MM-DD
 archive_search_refinement: "V1.1"
 
 # GitHub branch names used when the docs have links to GitHub
-source_branch_name: release-1.1
+source_branch_name: master
 doc_branch_name: master
 
 # The list of supported versions described by the docs