**docs**: remove status field from SB object

[#172646313](https://www.pivotaltracker.com/story/show/172646313)

Author: Derik Evangelista

docs/v3/source/includes/api_resources/_service_brokers.erb

@@ -3,7 +3,6 @@
   "guid": "dde5ad2a-d8f4-44dc-a56f-0452d744f1c3",
   "name": "my_service_broker",
   "url": "https://example.service-broker.com",
-  "status": "available",
   "created_at": "2015-11-13T17:02:56Z",
   "updated_at": "2016-06-08T16:41:26Z",
   "relationships": {
@@ -54,7 +53,6 @@
       "guid": "dde5ad2a-d8f4-44dc-a56f-0452d744f1c3",
       "name": "my_service_broker",
       "url": "https://example.service-broker.com",
-      "status": "available",
       "created_at": "2015-11-13T17:02:56Z",
       "updated_at": "2016-06-08T16:41:26Z",
       "relationships": {} ,
@@ -75,7 +73,6 @@
       "guid": "7aa37bad-6ccb-4ef9-ba48-9ce3a91b2b62",
       "name": "another_service_broker",
       "url": "https://another-example.service-broker.com",
-      "status": "available",
       "created_at": "2015-11-13T17:02:56Z",
       "updated_at": "2016-06-08T16:41:26Z",
       "relationships": {

docs/v3/source/includes/experimental_resources/service_brokers/_jobs.md.erb

@@ -1,11 +1,11 @@
 ### Service Broker Jobs
 
-CRUD operations for service brokers are asynchronous. `create`, `update` and `delete` endpoints return urls to `jobs` in the `Location` header of the HTTP response.
+CRUD operations for service brokers are asynchronous. `create`, `update` and `delete` endpoints include a job URL in the `Location` header of the HTTP response.
 
-These jobs are the only source of information about the progress and end state of the operation. Therefore, the job must be polled to find out when the process ends and if it was successful.
-It's also worth noting that there is no mechanism to link a service broker with its jobs, apart from the `Location` header in the API response.
+These jobs are the only source of information about the progress of the operation. Therefore, the job must be polled to find out when the process ends and if it was successful.
+There is no mechanism to link a service broker with its jobs, apart from the `Location` header in the API response.
 
-When a failure occurs during a create job, then the service broker won't be usable. However it will still be included in the `GET` endpoints responses, hence the importance of querying the job to find out the end status.
+When a failure occurs during a create job, the service broker won't be usable. It will still be included in the `GET` endpoints responses, hence the importance of querying the job to find out the end status.
 
-When updating a service broker, the changes will be rollbacked in the event the job fails. The service broker will remain unchanged with no indication that the update operation failed. Querying the job will provide such information.
+When updating a service broker, the changes will be rolled-back in the event of the job failing. The service broker will remain unchanged with no indication that the update operation failed. Querying the job will provide such information.