Issue 2755 - Troubleshooting PRs (knative#2854)

* Started work on updating contributing docs for different troubleshooting issues

* Updated formatting

* added section to default to reaching out in docs if you have additional issues

* Updated based on reviews

* Removed trailing spaces

* basic edit of development.md to match docs - still wip

* added newline to end of file

* Removed serving reference and updated based on reviews/comments

* Removed empty sections

* Cleaned up trailing whitespace

Author: Mike Petersen

DEVELOPMENT.md

@@ -0,0 +1,47 @@
+# Development
+
+This doc explains how to setup a development environment so you can get started
+[contributing](https://www.knative.dev/contributing/) to `Knative Docs`. Also
+take a look at:
+
+- [The pull request workflow](https://www.knative.dev/contributing/contributing/#pull-requests)
+
+## Prerequisites
+
+Follow the instructions below to set up your development environment. Once you
+meet these requirements, you can make changes and
+
+Before submitting a PR, see also [CONTRIBUTING.md](./CONTRIBUTING.md).
+
+### Sign up for GitHub
+
+Start by creating [a GitHub account](https://github.com/join), then setup
+[GitHub access via SSH](https://help.github.com/articles/connecting-to-github-with-ssh/).
+
+### Checkout your fork
+
+To check out this repository:
+
+1. Create your own
+   [fork of this repo](https://help.github.com/articles/fork-a-repo/)
+1. Clone it to your machine:
+
+```shell
+mkdir -p ${GOPATH}/src/knative.dev
+cd ${GOPATH}/src/knative.dev
+git clone [email protected]:${YOUR_GITHUB_USERNAME}/docs.git
+cd docs
+git remote add upstream https://github.com/knative/docs.git
+git remote set-url --push upstream no_push
+```
+
+_Adding the `upstream` remote sets you up nicely for regularly
+[syncing your fork](https://help.github.com/articles/syncing-a-fork/)._
+
+### Common Troubleshooting issues for PRs
+
+1. The CLA check fails even though you have signed the CLA. This may occur if you accept and commit suggestions in a pull request from another person's account, because the email address of that account doesn't match the address on record for the CLA. The commit will show up as co-authored, which can cause issues if your public email address has not signed the CLA.
+
+1. One or more tests are failing. If you do not see a specific error related to a change you made, and instead the errors are related to timeouts, try rerunning the test at a later time. There are running tasks that could result in timeouts or rate limiting if your test runs at the same time.
+
+1. Other Issues/Unsure - reach out in the #docs slack channel and someone will be happy to help out.