Part 2 of PR openservicebrokerapi#579

I missed this part of the spec that had similar text to what we edited
as part of openservicebrokerapi#579.

So this is part 2 of that PR.

Signed-off-by: Doug Davis <[email protected]>

spec.md

@@ -1385,9 +1385,9 @@ $ curl http://username:password@service-broker-url/v2/service_instances/:instanc
 | 409 Conflict | MUST be returned if a Service Binding with the same id, for the same Service Instance, already exists but with different parameters. |
 | 422 Unprocessable Entity | MUST be returned if the Service Broker requires that `app_guid` be included in the request body. The response body MUST contain error code `"RequiresApp"` (see [Service Broker Errors](#service-broker-errors)). The error response MAY include a helpful error message in the `description` field such as `"This Service supports generation of credentials through binding an application only."`. Additionally, if the Service Broker rejects the request due to a concurrent request to create a Service Binding for the same Service Instance, then this error MUST be returned (see [Blocking Operations](#blocking-operations)). This MUST also be returned if the Service Broker only supports asynchronous bindings for the Service Instance and the request did not include `?accepts_incomplete=true`. In this case, the response body MUST contain error code `"AsyncRequired"` (see [Service Broker Errors](#service-broker-errors)). The error response MAY include a helpful error message in the `description` field such as `"This Service Instance requires client support for asynchronous binding operations."`. |
 
-Responses with any other status code MUST be interpreted as a failure and an
-unbind request MUST be sent to the Service Broker to prevent an orphan being
-created on the Service Broker. However, while the platform will attempt
+Responses with any other status code MUST be interpreted as a failure. See
+the [Orphans](#orphans) section for more information related to whether
+orphan mitigation needs to be applied. While a Platform might attempt
 to send an unbind request, Service Brokers MAY automatically delete
 any resources associated with the failed bind request on their own.