Add content about editing Kubernetes source code.

Author: steveperry-53

docs/home/contribute/generated-reference/kubernetes-components.md

@@ -38,7 +38,80 @@ information, see
 
 {% capture steps %}
 
-## Overview
+## Getting two repositories
+
+If you don't already have the `kubernetes/website` repository, get it now:
+
+```shell
+mkdir $GOPATH/src
+cd $GOPATH/src
+go get github.com/kubernetes/website
+```
+
+Determine the base directory of your clone of the
+[kubernetes/website](https://github.com/kubernetes/website) repository.
+For example, if you followed the preceding step to get the repository,
+your base directory is `$GOPATH/src/github.com/kubernetes/website.`
+The remaining steps refer to your base directory as `<web-base>`.
+
+If you plan on making changes to the ref docs, and if you don't already have
+the `kubernetes/kubernetes` repository, get it now:
+
+```shell
+mkdir $GOPATH/src
+cd $GOPATH/src
+go get github.com/kubernetes/kubernetes
+```
+
+Determine the base directory of your clone of the
+[kubernetes/kubernetes](https://github.com/kubernetes/kubernetes) repository.
+For example, if you followed the preceding step to get the repository,
+your base directory is `$GOPATH/src/github.com/kubernetes/kubernetes.`
+The remaining steps refer to your base directory as `<k8s-base>`.
+
+**Note:**
+If you only need to generate, but not change, the reference docs, you don't need to
+manually get the `kubernetes/kubernetes` repository. When you run the `update-imported-docs`
+tool, it will automatically clone the the `kubernetes/kubernetes` repository.
+{: .note}
+
+## Editing the Kubernetes source code
+
+The reference documentation for the Kubernetes components and tools is automatically
+generated from the Kubernetes source code. If you want to change the reference documentation,
+the first step is to change one or more comments in the Kubernetes source code. Make the
+change in your local kubernetes/kubernetes repository, and then submit a pull request to
+the master branch of
+[github.com/kubernetes/kubernetes](https://github.com/kubernetes/kubernetes).
+
+[PR 56942](https://github.com/kubernetes/kubernetes/pull/56942)
+is an example of a pull request that makes changes to comments in the Kubernetes
+source code.
+
+Monitor your pull request, and respond to reviewer comments. Continue to monitor
+your pull request until it is merged into the master branch of the
+kubernetes/kubernetes repository.
+
+## Cherry picking your change into a release branch
+
+Your change is now in the master branch, which is used for development of the next
+Kubernetes release. If you want your change to appear in the docs for a Kubernetes
+version that has already been released, you need to propose that your change be cherry
+picked into the release branch.
+
+For example, suppose the master branch is being used to develop Kubernetes 1.10, and
+you want to backport your change to the release-1.9 branch. For instructions on how
+to do this, see
+[Propose a Cherry Pick](https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md).
+
+Monitor your cherry-pick pull request until it is merged into the release branch.
+
+**Note:** Proposing a cherry pick requires that you have permission to set a label
+and a milestone in your pull request. If you don’t have those permissions, you will
+need to work with someone who can set the label and milestone for you.
+{: .note}
+
+## Overview update-imported-docs
 
 The `update-imported-docs` tool performs these steps: