Fix problem links (#6382)

* Fix problem links

Some of these changes need to go into the API repo as well.

* Update content/pt-br/news/releases/0.x/announcing-0.1/index.md

Co-Authored-By: Jhon Mike <jhon.msdev@gmail.com>

Co-authored-by: Jhon Mike <jhon.msdev@gmail.com>

content/en/docs/reference/config/policy-and-telemetry/istio.mixer.v1.config.client/index.html

@@ -375,7 +375,7 @@ Yes
 <p>EXPERIMENTAL:</p>
 
 <p>ecmascript style regex-based match as defined by
-<a href="http://en.cppreference.com/w/cpp/regex/ecmascript">EDCA-262</a>. For
+<a href="http://en.cppreference.com/w/cpp/regex">EDCA-262</a>. For
 example,</p>
 
 <pre><code>&quot;^/pets/(.*?)?&quot;

content/en/news/releases/0.x/announcing-0.1/index.md

@@ -47,7 +47,7 @@ Google, IBM and Lyft joined forces to create Istio from a desire to provide a re
 
 **Policy Driven Ops**: Istio empowers teams with different areas of concern to operate independently. It decouples cluster operators from the feature development cycle, allowing improvements to security, monitoring, scaling, and service topology to be rolled out *without* code changes. Operators can route a precise subset of production traffic to qualify a new service release. They can inject failures or delays into traffic to test the resilience of the service mesh, and set up rate limits to prevent services from being overloaded. Istio can also be used to enforce compliance rules, defining ACLs between services to allow only authorized services to talk to each other.
 
-**Secure by default**: It is a common fallacy of distributed computing that the network is secure. Istio enables operators to authenticate and secure all communication between services using a mutual TLS connection, without burdening the developer or the operator with cumbersome certificate management tasks. Our security framework is aligned with the emerging [SPIFFE](https://spiffe.github.io/) specification, and is based on similar systems that have been tested extensively inside Google.
+**Secure by default**: It is a common fallacy of distributed computing that the network is secure. Istio enables operators to authenticate and secure all communication between services using a mutual TLS connection, without burdening the developer or the operator with cumbersome certificate management tasks. Our security framework is aligned with the emerging [SPIFFE](https://spiffe.io/) specification, and is based on similar systems that have been tested extensively inside Google.
 
 **Incremental Adoption**: We designed Istio to be completely transparent to the services running in the mesh, allowing teams to incrementally adopt features of Istio over time. Adopters can start with enabling fleet-wide visibility and once they’re comfortable with Istio in their environment they can switch on other features as needed.
 

content/pt-br/docs/reference/config/security/istio.authentication.v1alpha1/index.html

@@ -674,7 +674,7 @@ Yes
 <td><code>regex</code></td>
 <td><code>string (oneof)</code></td>
 <td>
-<p>ECMAscript style regex-based match as defined by <a href="http://en.cppreference.com/w/cpp/regex/ecmascript">EDCA-262</a>.
+<p>ECMAscript style regex-based match as defined by <a href="http://en.cppreference.com/w/cpp/regex">EDCA-262</a>.
 Example: &ldquo;^/pets/(.*?)?&rdquo;</p>
 
 </td>

content/pt-br/news/releases/0.x/announcing-0.1/index.md

@@ -47,7 +47,7 @@ Google, IBM and Lyft joined forces to create Istio from a desire to provide a re
 
 **Policy Driven Ops**: Istio empowers teams with different areas of concern to operate independently. It decouples cluster operators from the feature development cycle, allowing improvements to security, monitoring, scaling, and service topology to be rolled out *without* code changes. Operators can route a precise subset of production traffic to qualify a new service release. They can inject failures or delays into traffic to test the resilience of the service mesh, and set up rate limits to prevent services from being overloaded. Istio can also be used to enforce compliance rules, defining ACLs between services to allow only authorized services to talk to each other.
 
-**Secure by default**: It is a common fallacy of distributed computing that the network is secure. Istio enables operators to authenticate and secure all communication between services using a mutual TLS connection, without burdening the developer or the operator with cumbersome certificate management tasks. Our security framework is aligned with the emerging [SPIFFE](https://spiffe.github.io/) specification, and is based on similar systems that have been tested extensively inside Google.
+**Secure by default**: It is a common fallacy of distributed computing that the network is secure. Istio enables operators to authenticate and secure all communication between services using a mutual TLS connection, without burdening the developer or the operator with cumbersome certificate management tasks. Our security framework is aligned with the emerging [SPIFFE](https://spiffe.io/) specification, and is based on similar systems that have been tested extensively inside Google.
 
 **Incremental Adoption**: We designed Istio to be completely transparent to the services running in the mesh, allowing teams to incrementally adopt features of Istio over time. Adopters can start with enabling fleet-wide visibility and once they’re comfortable with Istio in their environment they can switch on other features as needed.
 

content/zh/docs/reference/config/policy-and-telemetry/istio.mixer.v1.config.client/index.html

@@ -371,7 +371,7 @@ Yes
 <p>EXPERIMENTAL:</p>
 
 <p>ecmascript style regex-based match as defined by
-<a href="http://en.cppreference.com/w/cpp/regex/ecmascript">EDCA-262</a>. For
+<a href="http://en.cppreference.com/w/cpp/regex">EDCA-262</a>. For
 example,</p>
 
 <pre><code>&quot;^/pets/(.*?)?&quot;

content/zh/news/releases/0.x/announcing-0.1/index.md

@@ -46,7 +46,7 @@ Google、IBM 和 Lyft 为了共同的愿景，基于为内部和企业客户构
 
 **策略驱动运维**：Istio 赋予肩负不同职责的团队以独立操作的能力。它将集群管理员从应用部署环节中分离，这可以增强应用的安全、监测、伸缩和服务拓扑等能力而 *不需要* 变更代码。运维人员可以精确的路由一部分生产流量用于检验一个新版本的服务。他们可以在流量中注入故障和延迟来测试服务网格的适应能力，同时可以设置请求限制来放置服务被过载。Istio 也可以被用于确保合规，在服务间定义 ACL 可以仅允许被授权的服务才能相互访问。
 
-**默认安全**：一个常见的缪误是认为分布式计算的网络是安全的。Istio 使用双向 TLS 连接，使运维人员可以确保服务之间的通信是经过认证和安全的，而使开发者或运维人员无需负担繁重的认证管理任务。我们的安全框架符合 [SPIFFE](https://spiffe.github.io/) 规范，且基于在 Google 内部经过大范围测试的类似系统。
+**默认安全**：一个常见的缪误是认为分布式计算的网络是安全的。Istio 使用双向 TLS 连接，使运维人员可以确保服务之间的通信是经过认证和安全的，而使开发者或运维人员无需负担繁重的认证管理任务。我们的安全框架符合 [SPIFFE](https://spiffe.io/) 规范，且基于在 Google 内部经过大范围测试的类似系统。
 
 **渐进式适配**：我们有意使 Istio 对于运行于网格中的服务完全透明，这允许团队逐步适配 Istio 的功能。适配人员可以首先启用集群范围内的可见性，一旦他们适应了 Istio 的存在，他们可以按需开启其他功能。