Broken links

content/en/blog/_posts/2018-07-16-kubernetes-1-11-release-interview.md

@@ -267,7 +267,7 @@ TIM PEPPER: Also, I would maybe argue in a way that a portion of that wasn't jus
 
 <i>Thanks to Josh Berkus and Tim Pepper for talking to the Kubernetes Podcast from Google.
 
-[Josh Berkus](https://github.com/jberkus) hangs out in #sig-release on the [Kubernetes Slack](slack.k8s.io). He maintains a newsletter called "[Last Week in Kubernetes Development](http://lwkd.info/)", with Noah Kantrowitz. You can read him on Twitter at [@fuzzychef](https://twitter.com/fuzzychef), but he does warn you that there's a lot of politics there as well.
+[Josh Berkus](https://github.com/jberkus) hangs out in #sig-release on the [Kubernetes Slack](https://slack.k8s.io). He maintains a newsletter called "[Last Week in Kubernetes Development](http://lwkd.info/)", with Noah Kantrowitz. You can read him on Twitter at [@fuzzychef](https://twitter.com/fuzzychef), but he does warn you that there's a lot of politics there as well.
 
 
 [Tim Pepper](https://github.com/tpepper) is also on Slack - he's always open to folks reaching out with a question, looking for help or advice.  On Twitter you'll find him at [@pythomit](https://twitter.com/pythomit), which is "Timothy P" backwards. Tim is an avid soccer fan and season ticket holder for the [Portland Timbers](https://portlandtimbers.com/) and the [Portland Thorns](https://portlandthorns.com/), so you'll get all sorts of opinions on soccer in addition to technology!

content/en/blog/_posts/2019-02-12-building-a-kubernetes-edge-control-plane-for-envoy-v2.md

@@ -59,7 +59,7 @@ More crucially, though, the first implementation of the IR allowed rapid prototy
 
 ## Ambassador >= v0.50: Envoy v2 APIs (ADS), Testing with KAT, and Golang
 
-In consultation with the [Ambassador community](http://d6e.co/slack), the [Datawire](www.datawire.io) team undertook a redesign of the internals of Ambassador in 2018. This was driven by two key goals. First, we wanted to integrate Envoy's v2 configuration format, which would enable the support of features such as [SNI](https://www.getambassador.io/user-guide/sni/), [rate limiting](https://www.getambassador.io/user-guide/rate-limiting) and [gRPC authentication APIs](https://www.getambassador.io/user-guide/auth-tutorial). Second, we also wanted to do much more robust semantic validation of Envoy configuration due to its increasing complexity (particularly when operating with large-scale application deployments).
+In consultation with the [Ambassador community](http://d6e.co/slack), the [Datawire](https://www.datawire.io) team undertook a redesign of the internals of Ambassador in 2018. This was driven by two key goals. First, we wanted to integrate Envoy's v2 configuration format, which would enable the support of features such as [SNI](https://www.getambassador.io/user-guide/sni/), [rate limiting](https://www.getambassador.io/user-guide/rate-limiting) and [gRPC authentication APIs](https://www.getambassador.io/user-guide/auth-tutorial). Second, we also wanted to do much more robust semantic validation of Envoy configuration due to its increasing complexity (particularly when operating with large-scale application deployments).
 
 
 ### Initial stages

content/en/blog/_posts/2019-03-20-A-Look-Back-And-Whats-In-Store-For-Kubernetes-Contributor-Summits.md

@@ -19,7 +19,7 @@ We build the contributor summits around you:
   * docs
   * code
   * community management
-* [Subproject OWNERs] (aka maintainers in other OSS circles)
+* Subproject OWNERs (aka maintainers in other OSS circles)
 * Special Interest Group (SIG) / Working Group (WG) [Chair or Tech Lead]
 * Active Contributors
 * Casual Contributors
@@ -57,17 +57,17 @@ Jonas Rosland, Josh Berkus, Paris Pittman, Jorge Castro, Bob Killen, Deb Giles,
 
 ## Relive Seattle Contributor Summit 
 
-📈 80% growth rate since the Austin 2017 December event  
-📜 Event waiting list: 103  
-🎓 76 contributors were on-boarded through the New Contributor Workshop  
-🎉 92% of the current contributors RSVPs attended and of those:  
-👩🏻‍🚒 25% were [Special Interest Group] or Working Group Chairs or Tech Leads  
-🗳 70% were eligible to vote in the last [steering committee election] (more than 50 contributions in 2018)   
-📹 20+ [Sessions]  
-👀 Most watched to date: Technical Vision, Security, API Code Base Tour  
-🌟 Top 3 according to survey: Live API Code Review, Deflaking Unconference, Technical Vision  
-🎱 🎳 160 attendees for the social at [Garage] on Sunday night where we sunk eight balls and recorded strikes (out in some cases)  
-🏆 Special recognition: SIG Storage, @dims, and @jordan  
+📈 80% growth rate since the Austin 2017 December event
+📜 Event waiting list: 103
+🎓 76 contributors were on-boarded through the New Contributor Workshop
+🎉 92% of the current contributors RSVPs attended and of those:
+👩🏻‍🚒 25% were [Special Interest Group] or Working Group Chairs or Tech Leads
+🗳 70% were eligible to vote in the last steering committee election (more than 50 contributions in 2018)
+📹 20+ [Sessions]
+👀 Most watched to date: Technical Vision, Security, API Code Base Tour
+🌟 Top 3 according to survey: Live API Code Review, Deflaking Unconference, Technical Vision
+🎱 🎳 160 attendees for the social at [Garage] on Sunday night where we sunk eight balls and recorded strikes (out in some cases)
+🏆 Special recognition: SIG Storage, @dims, and @jordan
 📸 Pictures (special thanks to [rdodev])
 Garage Pic
 Reg Desk

content/id/docs/concepts/overview/kubernetes-api.md

@@ -11,11 +11,11 @@ card:
 
 Secara keseluruhan standar yang digunakan untuk API dijelaskan di dalam [dokumentasi API standar](https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md).
 
-<i>Endpoints API</i>, <i>resource types</i> serta contoh penggunaan dijelaskan di dalam [API Reference](/en/docs/reference).
+<i>Endpoints API</i>, <i>resource types</i> serta contoh penggunaan dijelaskan di dalam [API Reference](/docs/reference).
 
-Akses <i>remote</i> penggunaan API dijelaskan di dalam [dokumentasi akses API](/en/docs/reference/access-authn-authz/controlling-access/).
+Akses <i>remote</i> penggunaan API dijelaskan di dalam [dokumentasi akses API](/docs/reference/access-authn-authz/controlling-access/).
 
-API Kubernetes juga berperan sebagai skema konfigurasi yang deklaratif di dalam sistem.. Sementara itu, [kubectl](/en/docs/reference/kubectl/overview/) merupakan <i>command-line</i> yang dapat digunakan untuk membuat, menmperbaharui, menghapus, dan mendapatkan obyek API. 
+API Kubernetes juga berperan sebagai skema konfigurasi yang deklaratif di dalam sistem.. Sementara itu, [kubectl](/docs/reference/kubectl/overview/) merupakan <i>command-line</i> yang dapat digunakan untuk membuat, menmperbaharui, menghapus, dan mendapatkan obyek API.
 
 Kubernetes menyimpan bentuk terserialisasi dari obyek API yang dimilikinya di dalam [etcd](https://coreos.com/docs/distributed-configuration/getting-started-with-etcd/).
 

content/id/docs/reference/glossary/platform-developer.md

@@ -14,4 +14,4 @@ tags:
 
 <!--more--> 
 
-Pengembang platform dapat, misalnya, menggunakan [Sumber Daya Kustom](/docs/concept/api-extension/custom-resources/) atau [Memperluas API Kubernetes dengan lapisan agregasi](/docs/concept/api-extension/apiserver-aggregation/) untuk menambahkan fungsionalitas ke instansi Kubernetes mereka, khususnya untuk aplikasi mereka. Beberapa Pengembang Platform juga {{<glossary_tooltip text = "kontributor" term_id = "contributor">}} dan mengembangkan perluasan yang berkontribusi pada komunitas Kubernetes. Lainnya mengembangkan sumber tertutup komersial atau perluasan spesifik situs.
+Pengembang platform dapat, misalnya, menggunakan [Sumber Daya Kustom](/docs/concept/extend-kubernetes/api-extension/custom-resources/) atau [Memperluas API Kubernetes dengan lapisan agregasi](/docs/concept/extend-kubernetes/api-extension/apiserver-aggregation/) untuk menambahkan fungsionalitas ke instansi Kubernetes mereka, khususnya untuk aplikasi mereka. Beberapa Pengembang Platform juga {{<glossary_tooltip text = "kontributor" term_id = "contributor">}} dan mengembangkan perluasan yang berkontribusi pada komunitas Kubernetes. Lainnya mengembangkan sumber tertutup komersial atau perluasan spesifik situs.

content/ko/docs/concepts/workloads/controllers/replicaset.md

@@ -219,12 +219,12 @@ API 버전에 대해서는 `frontend.yaml` 예제의 첫 번째 줄을 참고한
 우리는 `frontend.yaml` 예제에서 `tier: frontend`이라는 레이블을 하나 가지고 있다.
 이 파드를 다른 컨트롤러가 취하지 않도록 다른 컨트롤러의 셀렉터와 겹치지 않도록 주의해야 한다.
 
-템플릿의 [재시작 정책](ko/docs/concepts/workloads/Pods/pod-lifecycle/#restart-policy) 필드인 
+템플릿의 [재시작 정책](/ko/docs/concepts/workloads/Pods/pod-lifecycle/#restart-policy) 필드인
 `.spec.template.spec.restartPolicy`는 기본값인 `Always`만 허용된다.
 
 ### 파드 셀렉터
 
-`.spec.selector` 필드는 [레이블 셀렉터](ko/docs/concepts/overview/working-with-objects/labels/)이다.
+`.spec.selector` 필드는 [레이블 셀렉터](/ko/docs/concepts/overview/working-with-objects/labels/)이다.
 [앞서](#레플리카-셋의-작동-방식) 논의한 것처럼 이 레이블은 소유될 가능성이 있는 파드를 식별하는데 사용된다.
 우리 `frontend.yaml` 예제에서의 셀렉터는 다음과 같다.
 ```shell