Actually, I don't think this step is necessary.  I think it's fine to say the procedure is just:
* Get opinions on astropy-dev, make sure it seems like something APE-able.
* Issue a PR on astropy-APEs, and post on astropy-dev that the APE exists.

That is, mostly remove this paragraph, but add a mention in the second paragraph that when the PR to `astropy-APEs` is issued, they must post to astropy-dev that it exists.

Otherwise, there's two different media for the APE - one copy on the mailing list and another on github, and it'll be difficult to keep track when something gets updated, as that isn't reflected in the mailing list copy.