diff options
| author | Tim Pepper <tpepper@vmware.com> | 2018-01-22 16:47:37 -0800 |
|---|---|---|
| committer | Tim Pepper <tpepper@vmware.com> | 2018-01-24 11:56:01 -0800 |
| commit | 53f3badbe895823160387b7199ca97eb81479e6f (patch) | |
| tree | 98e4f445f2ca61f26e5040f2e65246a661051495 | |
| parent | f73383caa9cd8cef9a7aa5d18cf4106ad70de847 (diff) | |
contrib guide: tighten some language
The difference between the two links for communications around questions
and troubleshooting was not clear to me, and the wording made them
seem somewhat redundant. They're really two separate topic links,
so I've changed the wording to hopefully make it more clear that one has
general communications information and once is actually a
troubleshooting guide.
Signed-off-by: Tim Pepper <tpepper@vmware.com>
| -rw-r--r-- | contributors/guide/README.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/guide/README.md b/contributors/guide/README.md index 341e9fca..279c38bd 100644 --- a/contributors/guide/README.md +++ b/contributors/guide/README.md @@ -128,7 +128,7 @@ For quick reference on contributor resources, we have a handy [contributor cheat It is best to contact your [SIG](#learn-about-sigs) for issues related to the SIG's topic. Your SIG will be able to help you much more quickly than a general question would. -For questions and troubleshooting, please feel free to use any of the methods of communication listed [here](/communication.md). The [kubernetes website](https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/) also lists this information. +For general questions and troubleshooting, use the [kubernetes standard lines of communication](/communication.md) and work through the [kubernetes troubleshooting guide](https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/). ## GitHub workflow |