remove refs to removed section

Signed-off-by: Craig <[email protected]>

Author: craig-osterhout

content/reference/api/registry/_index.md

@@ -673,13 +673,13 @@ response format is as follows:
 
 ### Deleting an image
 
-To delete a manifest, perform a DELETE request to a path in the following format: `/v2/<name>/manifests/<digest>` <sup>[end-9](#endpoints)</sup>
+To delete a manifest, perform a DELETE request to a path in the following format: `/v2/<name>/manifests/<digest>`
 
 <name> is the namespace of the repository, and <digest> is the digest of the manifest to be deleted. Upon success, the registry must respond with a 202 Accepted code. If the repository does not exist, the response must return 404 Not Found. If manifest deletion is disabled, the registry must respond with either a 400 Bad Request or a 405 Method Not Allowed.
 
 In the event that a manifest cannot be deleted because it is referenced by another manifest, it will return 403.
 
-Once deleted, a GET to '`/v2/<name>/manifests/<digest>` <sup>[end-9](#endpoints)</sup> and any tag pointing to that digest will return a 404.
+Once deleted, a GET to '`/v2/<name>/manifests/<digest>` and any tag pointing to that digest will return a 404.
 
 When deleting an image manifest that contains a subject field, and the referrers API returns a 404, clients should: