Fix "Stack Overflow" across docs.

community-membership.md

@@ -44,7 +44,7 @@ Members are expected to remain active contributors to the community.
 - Have contributed to the project or community.  Contribution may include, but is not limited to:
   - Authoring or reviewing PRs on GitHub
   - Filing or commenting on issues on GitHub
-  - Contributing to SIG or community discussions (e.g. meetings, Slack, email discussion forums, Stackoverflow, meetups)
+  - Contributing to SIG or community discussions (e.g. meetings, Slack, email discussion forums, Stack Overflow, meetups)
 - Sponsored by 2 members
   - TODO: Define the exact process for sponsorship.
 - Have read the [developer guide](contributors/devel/README.md)
@@ -60,10 +60,10 @@ TODO: Define a process for reviewing memberships.
   - Code is well tested
   - Tests consistently pass
   - Addresses bugs or issues discovered after code is accepted
-  
+
 **Note:** members who frequently contribute code are expected to proactively perform code reviews and work towards
 becoming a primary *reviewer* for the area that they are active in.
-  
+
 ## Reviewer
 
 Reviewers are able to review code for quality and correctness on some part of the project.

contributors/devel/on-call-build-cop.md

@@ -12,8 +12,8 @@ Your job is to be
 the first responder to all new issues. If you are not equipped to do
 this (which is fine!), it is your job to seek guidance!
 
-  * Support issues should be closed and redirected to Stackoverflow (see example
-response below).
+  * Support issues should be closed and redirected to Stack Overflow (see example
+response [here](on-call-user-support.md#user-support-response-example)).
 
   * All incoming issues should be tagged with a team label
 (team/{api,ux,control-plane,node,cluster,csi,redhat,mesosphere,gke,release-infra,test-infra,none});
@@ -49,36 +49,6 @@ person in rotation: try to ensure that every issue that gets filed while you are
 on duty is handled. The Github query to find issues with no team/* label is:
 [here](https://github.com/kubernetes/kubernetes/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+-label%3Ateam%2Fcontrol-plane+-label%3Ateam%2Fmesosphere+-label%3Ateam%2Fredhat+-label%3Ateam%2Frelease-infra+-label%3Ateam%2Fnone+-label%3Ateam%2Fnode+-label%3Ateam%2Fcluster+-label%3Ateam%2Fux+-label%3Ateam%2Fapi+-label%3Ateam%2Ftest-infra+-label%3Ateam%2Fgke+-label%3A"team%2FCSI-API+Machinery+SIG"+-label%3Ateam%2Fhuawei+-label%3Ateam%2Fsig-aws).
 
-Example response for support issues:
-
-```code
-Please re-post your question to [stackoverflow]
-(http://stackoverflow.com/questions/tagged/kubernetes).
-
-We are trying to consolidate the channels to which questions for help/support
-are posted so that we can improve our efficiency in responding to your requests,
-and to make it easier for you to find answers to frequently asked questions and
-how to address common use cases.
-
-We regularly see messages posted in multiple forums, with the full response
-thread only in one place or, worse, spread across multiple forums. Also, the
-large volume of support issues on github is making it difficult for us to use
-issues to identify real bugs.
-
-The Kubernetes team scans stackoverflow on a regular basis, and will try to
-ensure your questions don't go unanswered.
-
-Before posting a new question, please search stackoverflow for answers to
-similar questions, and also familiarize yourself with:
-
-  * [user guide](http://kubernetes.io/docs/user-guide/)
-  * [troubleshooting guide](http://kubernetes.io/docs/admin/cluster-troubleshooting/)
-
-Again, thanks for using Kubernetes.
-
-The Kubernetes Team
-```
-
 ### Build-copping
 
 * The [merge-bot submit queue](http://submit-queue.k8s.io/)

contributors/devel/on-call-user-support.md

@@ -2,21 +2,21 @@
 
 ### Traffic sources and responsibilities
 
-* [StackOverflow](http://stackoverflow.com/questions/tagged/kubernetes) and
+* [Stack Overflow](http://stackoverflow.com/questions/tagged/kubernetes) and
 [ServerFault](http://serverfault.com/questions/tagged/google-kubernetes):
 Respond to any thread that has no responses and is more than 6 hours old (over
 time we will lengthen this timeout to allow community responses). If you are not
 equipped to respond, it is your job to redirect to someone who can.
 
-  * [Query for unanswered Kubernetes StackOverflow questions](http://stackoverflow.com/search?tab=newest&q=%5bkubernetes%5d%20answers%3a0)
+  * [Query for unanswered Kubernetes Stack Overflow questions](http://stackoverflow.com/search?tab=newest&q=%5bkubernetes%5d%20answers%3a0)
   * [Query for unanswered Kubernetes ServerFault questions](https://serverfault.com/search?tab=newest&q=%5bgoogle-kubernetes%5d%20answers%3a0)
-  * Direct poorly formulated questions to [stackoverflow's tips about how to ask](http://stackoverflow.com/help/how-to-ask)
-  * Direct off-topic questions to [stackoverflow's policy](http://stackoverflow.com/help/on-topic)
+  * Direct poorly formulated questions to [Stack Overflow's tips about how to ask](http://stackoverflow.com/help/how-to-ask)
+  * Direct off-topic questions to [Stack Overflow's policy](http://stackoverflow.com/help/on-topic)
 
 * [Slack](https://kubernetes.slack.com) ([registration](http://slack.k8s.io)):
 Your job is to be on Slack, watching for questions and answering or redirecting
-as needed, such as to a SIG-specific channel. Please especially watch 
-`#kubernetes-users` and `#kubernetes-novice`. Also check out the 
+as needed, such as to a SIG-specific channel. Please especially watch
+`#kubernetes-users` and `#kubernetes-novice`. Also check out the
 [Slack Archive](http://kubernetes.slackarchive.io/).
 
 * [Email/Groups](https://groups.google.com/forum/#!forum/kubernetes-users):
@@ -25,20 +25,22 @@ time we will lengthen this timeout to allow community responses). If you are not
 equipped to respond, it is your job to redirect to someone who can.
 
 *  on slack: Respond to questions that
-don't get answers. 
+don't get answers.
 
 In general, try to direct support questions to:
 
 1. Documentation, such as the [user documentation](https://kubernetes.io/docs/) and
 [troubleshooting guide](https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/)
 
-2. Stackoverflow
+2. Stack Overflow
+
+#### User support response example
 
 If you see questions on [email protected], try to redirect them
-to Stackoverflow. Example response:
+to Stack Overflow. Example response:
 
 ```code
-Please re-post your question to [stackoverflow]
+Please re-post your question to [Stack Overflow]
 (http://stackoverflow.com/questions/tagged/kubernetes).
 
 We are trying to consolidate the channels to which questions for help/support
@@ -51,10 +53,10 @@ thread only in one place or, worse, spread across multiple forums. Also, the
 large volume of support issues on github is making it difficult for us to use
 issues to identify real bugs.
 
-The Kubernetes team scans stackoverflow on a regular basis, and will try to
+The Kubernetes team scans Stack Overflow on a regular basis, and will try to
 ensure your questions don't go unanswered.
 
-Before posting a new question, please search stackoverflow for answers to
+Before posting a new question, please search Stack Overflow for answers to
 similar questions, and also familiarize yourself with:
 
   * [user documentation](http://kubernetes.io/docs/)
@@ -66,7 +68,7 @@ The Kubernetes Team
 ```
 
 If you answer a question (in any of the above forums) that you think might be
-useful for someone else in the future, please send a PR or file an issue in 
+useful for someone else in the future, please send a PR or file an issue in
 [kubernetes.github.io](https://github.com/kubernetes/kubernetes.github.io).
 
 ### Contact information

project-managers/README.md

@@ -8,16 +8,16 @@ expected to:
 * Set the milestone on a PR or issue
 * Assign issues to the correct people for immediate triage/work
 * Assign PRs to be reviewed by the correct people
-* Close duplicate, stale, misplaced issues 
-* Close support issues, with a redirect to stackoverflow
+* Close duplicate, stale, misplaced issues
+* Close support issues, with a redirect to Stack Overflow
 
 They should **NOT**:
 
 * Manually apply merge labels to PRs (lgtm, approved) or press merge button
 * Apply priority labels to PRs
 * Apply cherrypick labels to PRs
 * Edit text of other people's PRs and issues, including deleting comments
-* Modify anyone else's release note 
+* Modify anyone else's release note
 * Create, edit, delete labels
 * Create, edit, close, delete milestones
 * Create, edit, delete releases
@@ -41,6 +41,6 @@ The following is the provisional process for adding people to the group:
 
 The Contributor Experience working-group leads or Brian Grant (@bgrant0607) will approve or deny your request.
 
-Some prerequisites may need to be completed prior to being added to the github team, such as clarifying relevant policies in our contributor documentation. 
+Some prerequisites may need to be completed prior to being added to the github team, such as clarifying relevant policies in our contributor documentation.
 
 Thanks for helping to manage the project!