address review feedback

Author: toumorokoshi

aep/general/0164/aep.md.j2

@@ -62,17 +62,23 @@ A resource that supports soft delete **should** provide an `Undelete` method:
 
 ### Create
 
-If a user attempts a create on a soft-deleted resource, the request **must**
-succeed, acting as if the resource did not exist previously.
+Create methods **must** adhere to one of the following:
+
+- If a user attempts a create on a soft-deleted resource, the create **must**
+  succeed, acting as if the resource did not exist previously.
+- The create must accept a field (query parameter for OAS),
+  `overwrite_soft_deleted`. If set to `false`, the request **must** fail if a
+  soft-deleted resource exists. If set to `true`, the request **must** succeed
+  if the resource exists acting as if the resource did not exist previously.
 
 ### List and Get
 
 Soft-deleted resources **must not** be returned in `List` AEP-132 responses by
 default (unless `bool show_deleted` is true).
 
 A `Get` AEP-131 request for a soft deleted resource **must** return with a
-`410 Gone` response unless `bool show_deleted` is true, in which case
-soft-deleted resources **must** return the resource.
+`404 Not Found` response unless `bool show_deleted` is true, in which case
+soft-deleted resources **must** return the resource (with the `DELETED` state value if the resource includes a [`state` field](/states)).
 
 Services that soft delete resources **may** choose a reasonable strategy for
 purging those resources, including automatic purging after a reasonable time