diff --git a/docs/spec/api.md b/docs/spec/api.md
index c573178..12c1043 100644
--- a/docs/spec/api.md
+++ b/docs/spec/api.md
@@ -175,7 +175,6 @@ identify a set of modifications.
       <li>Added error code for unsupported operations.</li>
     </ul>
   </dd>
-
 </dl>

 ## Overview
@@ -727,7 +726,8 @@ delete may be issued with the following request format:

     DELETE /v2/<name>/blobs/<digest>

-If the blob exists and has been successfully deleted, the following response will be issued:
+If the blob exists and has been successfully deleted, the following response
+will be issued:

     202 Accepted
     Content-Length: None
@@ -735,6 +735,8 @@ If the blob exists and has been successfully deleted, the following response wil
 If the blob had already been deleted or did not exist, a `404 Not Found`
 response will be issued instead.

+If a layer is deleted which is referenced by a manifest in the registry,
+then the complete images will not be resolvable.

 #### Pushing an Image Manifest

@@ -1022,7 +1024,6 @@ A list of methods and URIs are covered in the table below:
 | PUT | `/v2/<name>/blobs/uploads/<uuid>` | Blob Upload | Complete the upload specified by `uuid`, optionally appending the body as the final chunk. |
 | DELETE | `/v2/<name>/blobs/uploads/<uuid>` | Blob Upload | Cancel outstanding upload processes, releasing associated resources. If this is not called, the unfinished uploads will eventually timeout. |
 | GET | `/v2/_catalog` | Catalog | Retrieve a sorted, json list of repositories available in the registry. |
-| DELETE | `/v2/<name>/blobs/<digest>` | Blob delete | Delete the blob identified by `name` and `digest`|


 The detail for each endpoint is covered in the following sections.
@@ -1732,7 +1733,6 @@ The error codes that may be included in the response body are enumerated below:

 #### DELETE Manifest

-
 Delete the manifest identified by `name` and `reference`. Note that a manifest can _only_ be deleted by `digest`.