Address review comments

Author: pisaychuk

site/docs/numbers/porting/loaUpload.mdx

@@ -39,7 +39,7 @@ export const Highlight = ({children, color}) => (
   );
 
 
-After successfully submitting the [Create LNP Order request](/docs/numbers/guides/porting/portingNumbers), an Letter of Authorization (LOA) may be uploaded using our LOA API.
+After successfully submitting the [Create LNP Order request](/docs/numbers/guides/porting/portingNumbers), a Letter of Authorization (LOA) may be uploaded using our LOA API.
 
 :::caution
 If your port-on order has a ```PENDING_DOCUMENTS``` status then LOA upload is a required action.

site/docs/numbers/porting/portingNumbers.mdx

@@ -186,7 +186,7 @@ curl 'https://dashboard.bandwidth.com/api/accounts/{BW_ACCOUNT_ID}/portins' \
 
 Porting numbers in the Bandwidth Dashboard is asynchronous which means the orders are processed and the order status is updated asynchronously. As times can vary and are not guaranteed Bandwidth recommends configuring your account with a subscription instead of polling the order resource for `<OrderStatus>`. Please follow the [How to setup Notification Webhook](/docs/numbers/webhooks/orderWebhook) guide.
 
-To poll an information about your port-in you can still use a <Highlight color="#00bf8c">GET</Highlight> request to [accounts/{accountId}/portins API](/apis/numbers/#operation/GetPortin). This can be done using tools like Postman or cURL.
+To poll for information about your port-in you can still use a <Highlight color="#00bf8c">GET</Highlight> request to [accounts/{accountId}/portins API](/apis/numbers/#operation/GetPortin). This can be done using tools like Postman or cURL.
 
 <Highlight color="#00bf8c">GET</Highlight> <code>https://dashboard.bandwidth.com/api/accounts/{accountId}/portins/{orderId}</code>
 <Tabs

site/docs/numbers/porting/updateBulkPortins.mdx

@@ -47,7 +47,7 @@ Subtending orders are created after telephone numbers are added to the bulk port
 
 ### Example
 
-In the following example we are adding ```LoaAuthorizingPerson``` field to the bulk port-in (to apply it to all future subtending port-in orders):
+In the following example we are adding ```LoaAuthorizingPerson``` field to the bulk port-in order (to apply it to all future subtending port-in orders):
 <Highlight color="#9a59c5">PUT</Highlight> <code>https://dashboard.bandwidth.com/api/accounts/{accountId}/bulkPortins/{orderId}</code>
 <Tabs
     groupId="putBulkPortin"

site/docs/numbers/porting/updatePortin.mdx

@@ -38,9 +38,9 @@ In this guide we will show you how to update your port-in order. We assume that
 
 ## Update Port-in Order
 
-The <code class="put">PUT</code> to [/portins/{orderId} API](/apis/numbers/#operation/UpdatePortin) API allows a user to modify an existing LNP order, by sending a so-called SUPP request. Modifications are only allowed for orders that are not yet `complete` or `cancelled`. Since many of the entries in an LNP Order cannot be changed after the initial order is placed, the ```PUT``` on a porting order-id does not require that the full order payload is included.
+The <code class="put">PUT</code> to [/portins/{orderId} API](/apis/numbers/#operation/UpdatePortin) API allows a user to modify an existing LNP order, by sending a SUPP request. Modifications are only allowed for orders that are not yet `complete` or `cancelled`. Since many of the entries in an LNP Order cannot be changed after the initial order is placed, the ```PUT``` on a porting order-id does not require that the full order payload is included.
 
-If the order ProcessingStatus is `DRAFT`, the rules about what can be changed are much more relaxed. Validation is performed when the ProcessingStatus is changed from `DRAFT` to `SUBMITTED`. The AltSpid element can be modified if it is not configured at the system level.
+If the order ProcessingStatus is `DRAFT`, the rules about what can be changed are much more lenient. Validation is performed when the ProcessingStatus is changed from `DRAFT` to `SUBMITTED`. The AltSpid element can be modified if it is not configured at the system level.
 Regarding the fields which can be updated for different port types check the request schema section of [PUT /portins/{orderId}](/apis/numbers/#operation/UpdatePortin) specification.
 
 The general approach to handling this API call is to replace the elements included in the request body, and leave other preexisting elements in an unmodified condition. This is typical of a PATCH method, but because of our commitment to backwards compatibility we have elected not to "Fix" this behavior. As a result, there are some elements that cannot be modified using the <Highlight color="#9a59c5">PUT</Highlight> method. The elements affected vary by port-in Order type, which can be determined using a <Highlight color="#00bf8c">GET</Highlight> request to the `/portins/{orderId}` endpoint.