Tweak the README.md stub verbiage to make it more clear first that th…

…ese repos aren't necessarily "official" in the "upstream partner official" sense, and second that changes being merged here do not necessarily translate directly into updated images

generate-repo-stub-readme.sh

@@ -22,9 +22,13 @@ hubPage="https://registry.hub.docker.com/_/$repo/"
 cat <<EOREADME
 # About this Repo
 
-This is the Git repo of the official Docker image for [$repo]($hubPage). See the Hub page for the full readme on how to use the Docker image and for information regarding contributing and issues.
+This is the Git repo of the Docker [official image](https://docs.docker.com/docker-hub/official_repos/) for [$repo]($hubPage). See [the Docker Hub page]($hubPage) for the full readme on how to use this Docker image and for information regarding contributing and issues.
 
 The full readme is generated over in [docker-library/docs]($gitRepo), specificially in [docker-library/docs/$repo]($gitRepo/tree/master/$repo).
 
+See a change merged here that doesn't show up on the Docker Hub yet? Check [the "library/$repo" manifest file in the docker-library/official-images repo](https://github.com/docker-library/official-images/blob/master/library/$repo), especially [PRs with the "library/$repo" label on that repo](https://github.com/docker-library/official-images/labels/library%2F$repo). For more information about the official images process, see the [docker-library/official-images readme](https://github.com/docker-library/official-images/blob/master/README.md).
+
 [![Travis CI](https://img.shields.io/travis/docker-library/$repo/master.svg)](https://travis-ci.org/docker-library/$repo/branches)
+
+<!-- THIS FILE IS GENERATED BY https://github.com/docker-library/docs/blob/master/generate-repo-stub-readme.sh -->
 EOREADME