Diego API documentation should be more easily discoverable

[shalako]

As a consumer of Diego, I care most about two things:

1. How to deploy it
2. Public interfaces

The README does mention use of CF, however Diego's API docs are buried in a docs directory in the Receptor repo (not even in the README for Receptor), to which there is no link on the diego-release README. I did eventually find a link to the API docs in the design notes repo.

The user experience would be improved if there were a link to the API docs on the README.

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/97939766.

[emalm]

Hi, @shalako,

Thanks very much for your feedback. The diego-release README now links to the receptor API docs on GitHub, towards the top of the document. Is that sufficiently discoverable?

As you requested in #56, we'll shortly be improving the documentation for operators deploying a stable or metastable diego-release alongside a given CF version.

Thanks again,
Eric

[shalako]

Much better. Thank you.