whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix indentation and Code of Conduct link in contribute section (#9896)

Browse Source 
Signed-off-by: GuessWhoSamFoo <sfoohei@gmail.com>
This commit is contained in:
Sam Foo
2018-08-18 06:51:06 -07:00
committed by k8s-ci-robot
parent 18ba9a10f4
commit 13184cac84
3 changed files with 39 additions and 39 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/workloads/pods/pod-lifecycle.md
+1 -1
View File
@@ -192,7 +192,7 @@ status:
The new Pod conditions must comply with Kubernetes [label key format](/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set). The new Pod conditions must comply with Kubernetes [label key format](/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set).
Since the `kubectl patch` command still doesn't support patching object status, Since the `kubectl patch` command still doesn't support patching object status,
the new Pod conditions have to be injected through the `PATCH` action using the new Pod conditions have to be injected through the `PATCH` action using
one of the [KubeClient libraries](/docs/reference/using-api/client-librarie/). one of the [KubeClient libraries](/docs/reference/using-api/client-libraries/).
With the introduction of new Pod conditions, a Pod is evaluated to be ready **only** With the introduction of new Pod conditions, a Pod is evaluated to be ready **only**
when both the following statements are true: when both the following statements are true:
content/en/docs/contribute/intermediate.md
+2 -2
View File
@@ -61,7 +61,7 @@ active participants.
Before you start reviewing PRs, make sure you are familiar with the Before you start reviewing PRs, make sure you are familiar with the
[Documentation Style Guide](/docs/contribute/style/style-guide/) [Documentation Style Guide](/docs/contribute/style/style-guide/)
and the [code of conduct]() <!-- TODO when #9355 is merged --> and the [code of conduct](/community/code-of-conduct/)
### Find a PR to review ### Find a PR to review
@@ -340,7 +340,7 @@ but the following guidelines apply:
use the pre-release feature branch created for that Kubernetes version. use the pre-release feature branch created for that Kubernetes version.
For more guidance, see For more guidance, see
[Choose which branch to use](docs/contribute/start#choose-which-git-branch-to-use). [Choose which branch to use](/docs/contribute/start/#choose-which-git-branch-to-use).
After you decide which branch to start your work (or _base it on_, in Git After you decide which branch to start your work (or _base it on_, in Git
terminology), use the following workflow to be sure your work is based on the terminology), use the following workflow to be sure your work is based on the
content/en/docs/contribute/start.md
+2 -2
View File
@@ -147,7 +147,7 @@ need more background in Git terminology.
{{< note >}} {{< note >}}
**Kubnetes code developers**: If you are documenting a new feature for an **Kubnetes code developers**: If you are documenting a new feature for an
upcoming Kubernetes release, your process is a bit different. See upcoming Kubernetes release, your process is a bit different. See
[Document a feature](/docs/contribute/intermediate.md#sig-members-documenting-new-features) for [Document a feature](/docs/contribute/intermediate/#sig-members-documenting-new-features) for
process guidelines and information about deadlines. process guidelines and information about deadlines.
{{< /note >}} {{< /note >}}
@@ -246,7 +246,7 @@ documentation.
**Create pull request**. **Create pull request**.
Congratulations! Your pull request is available in Congratulations! Your pull request is available in
Pull requests](https://github.com/kubernetes/website/pulls). [Pull requests](https://github.com/kubernetes/website/pulls).
After a few minutes, you can preview the website with your PR's changes After a few minutes, you can preview the website with your PR's changes
applied. Go to the **Conversation** tab of your PR and click the **Details** applied. Go to the **Conversation** tab of your PR and click the **Details**