From ecefdc9df22f20e83ab4caf5151bd1965a3c59c4 Mon Sep 17 00:00:00 2001 From: Jared Date: Wed, 18 Jan 2017 14:25:58 -0800 Subject: [PATCH 1/2] Add "Needs UX Review" tag I'd like to tag existing issues that are specifically UX related for triaging, since we have a graphic designer who can fix them. --- docs/contribute/review-issues.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/contribute/review-issues.md b/docs/contribute/review-issues.md index 8b16d450c6..38d4424c7b 100644 --- a/docs/contribute/review-issues.md +++ b/docs/contribute/review-issues.md @@ -4,7 +4,7 @@ title: Reviewing Documentation Issues {% capture overview %} -This page explains how you should review and prioritize documentation issues made for the [kubernetes/kubernetes.github.io](https://github.com/kubernetes/kubernetes.github.io){: target="_blank"} repository. The purpose is to provide a way to organize issues and make it easier to contribute to Kubernetes documentation. The following should be used as the standard way of prioritizing, labeling, and interacting with issues. +This page explains how documentation issues are reviewed and prioritized for the [kubernetes/kubernetes.github.io](https://github.com/kubernetes/kubernetes.github.io){: target="_blank"} repository. The purpose is to provide a way to organize issues and make it easier to contribute to Kubernetes documentation. The following should be used as the standard way of prioritizing, labeling, and interacting with issues. {% endcapture %} {% capture body %} @@ -26,6 +26,9 @@ Issues should be sorted into different buckets of work using the following label * Issues that are suggestions for better processes or site improvements that require community agreement to be implemented * Topics can be brought to SIG meetings as agenda items +#### Needs UX Review +* Issues that are suggestions for improving the user interface of the site or fixing a broken UX. + ### Prioritizing Issues The following labels and definitions should be used to prioritize issues. If you change the priority of an issues, please comment on the issue with your reasoning for the change. From f59094324eee014cd548d477e3721df3d71fd5ed Mon Sep 17 00:00:00 2001 From: Jared Date: Thu, 26 Jan 2017 12:08:42 -0800 Subject: [PATCH 2/2] grammar issue Fixed https://github.com/kubernetes/kubernetes.github.io/pull/2348 --- docs/getting-started-guides/centos/centos_manual_config.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/getting-started-guides/centos/centos_manual_config.md b/docs/getting-started-guides/centos/centos_manual_config.md index f51aacf477..7f8f5ea7f2 100644 --- a/docs/getting-started-guides/centos/centos_manual_config.md +++ b/docs/getting-started-guides/centos/centos_manual_config.md @@ -17,7 +17,7 @@ This is a getting started guide for CentOS. It is a manual configuration so you The Kubernetes package provides a few services: kube-apiserver, kube-scheduler, kube-controller-manager, kubelet, kube-proxy. These services are managed by systemd and the configuration resides in a central location: /etc/kubernetes. We will break the services up between the hosts. The first host, centos-master, will be the Kubernetes master. This host will run the kube-apiserver, kube-controller-manager and kube-scheduler. In addition, the master will also run _etcd_. The remaining hosts, centos-minion-n will be the nodes and run kubelet, proxy, cadvisor and docker. -All of then run flanneld as networking overlay. +All of them run flanneld as networking overlay. **System Information:**