Fix grammar errors, broken punctuation, and changelog ordering

changelog.mdx

@@ -46,7 +46,7 @@
 
 **Mining account management:**
 - Reward history with pagination
 - Account-level hashrate monitoring with configurable intervals (5m, 1h, 24h)
 - Fee and stratum connection details
 
 **Payout configuration:**
@@ -55,7 +55,7 @@
 
 **Worker monitoring:**
 - List online workers with pagination
 - Individual worker hashrate history
 
 **Watcher links:**
 - Create read-only access links with granular permissions (dashboard, rewards, workers)
@@ -101,22 +101,6 @@
 </CardGroup>
 </Update>
 
-<Update label="February 11, 2025">
-## API Documentation Updates
-**Sub-account transfer endpoints: add transactionId for correlation**
-
-The response of `/api/v4/sub-account/transfer` and `/api/v4/sub-account/transfer/history` includes the `transactionId` field.
-
-Use `transactionId` to correlate transfer operations with transfer history records.
-
-The `id` field in transfer history is deprecated. Replace `id` with `transactionId`.
-
-<CardGroup cols={2}>
-  <Card title="Sub-Account Transfer" href="/api-reference/sub-accounts/sub-account-transfer" icon="arrow-right-arrow-left" horizontal/>
-  <Card title="Get Sub-Account Transfer History" href="/api-reference/sub-accounts/get-sub-account-transfer-history" icon="clock-rotate-left" horizontal/>
-</CardGroup>
-</Update>
-
 <Update label="September 21, 2025">
 ## Documentation Updates
 **Clarified Book Ticker stream update interval**
@@ -144,6 +128,22 @@
 </CardGroup>
 </Update>
 
+<Update label="February 11, 2025">
+## API Documentation Updates
+**Sub-account transfer endpoints: add transactionId for correlation**
+
+The response of `/api/v4/sub-account/transfer` and `/api/v4/sub-account/transfer/history` includes the `transactionId` field.
+
+Use `transactionId` to correlate transfer operations with transfer history records.
+
+The `id` field in transfer history is deprecated. Replace `id` with `transactionId`.
+
+<CardGroup cols={2}>
+  <Card title="Sub-Account Transfer" href="/api-reference/sub-accounts/sub-account-transfer" icon="arrow-right-arrow-left" horizontal/>
+  <Card title="Get Sub-Account Transfer History" href="/api-reference/sub-accounts/get-sub-account-transfer-history" icon="clock-rotate-left" horizontal/>
+</CardGroup>
+</Update>
+
 <Update label="July 16, 2025">
 ## API Documentation Updates
 **Enhanced Query executed orders documentation**
@@ -188,7 +188,7 @@
 ## Public WebSocket Update
 **Added BookTicker WebSocket stream**
 
 New bookTicker stream added to WebSocket API, providing real-time updates of best bid/ask prices and quantities for markets. Includes subscription (bookTicker_subscribe) and unsubscription (bookTicker_unsubscribe) methods for managing the data feed.
 
 <Card title="ws - Book Ticker" href="/websocket/market-streams/book-ticker" icon="ticket" horizontal/>
 </Update>

platform/colocation.mdx

@@ -1,5 +1,5 @@
 ---
 title: "Colocation Services"
 sidebarTitle: "Colocation"
 description: "WhiteBIT offers professional-grade [colocation](https://docs.whitebit.com/glossary/#colocation) services for [high-frequency trading (HFT)](https://docs.whitebit.com/glossary/#high-frequency-trading-hft) and algorithmic trading operations. Place trading servers close to the exchange’s [matching engine](https://docs.whitebit.com/glossary/#matching-engine) to achieve minimal [latency](https://docs.whitebit.com/glossary/#latency) and enhanced trading performance."
 ---
@@ -31,7 +31,7 @@
     #### Network Setup
     - Network Speed: 10Gbit connectivity required
     - Instance Type: Dedicated EC2 instances (recommended)
     - Security: IP address pool required for allowlisting
 
     #### Region Selection
     - Primary: eu-central-1a (recommended)
@@ -41,7 +41,7 @@
   </Step>
   <Step title="Technical Integration">
     The technical team will assist with:
-    - Network configuration including aws cloud latency optimized proxy
+    - Network configuration including AWS cloud latency optimized proxy
     - Performance testing
     - Trading system integration
   </Step>

platform/oauth/overview.mdx

@@ -32,7 +32,7 @@ When the access token expires, the application can use a refresh token to obtain
 </Steps>
 ## Use Cases
 
-#### Trading Bots & Algorithmic Trading
+### Trading Bots & Algorithmic Trading
 Enable automated trading strategies without storing WhiteBIT credentials in third-party systems. Trading bots can place, modify, and cancel orders while only having the specific permissions they need.
 
 ### Portfolio Trackers & Analytics

platform/webhook.mdx

@@ -60,11 +60,11 @@ Passing one of these checks enables the webhook.
 
 ### For processing web-hook requests
 
-All web hook requests are performing using POST method and with application/json content type. Consumer server should respond with 200 HTTP status code. If consumer was unable to handle web-hook, the request will be retry every 10 minutes but not more than 5 times.
+All webhook requests are performed using the POST method with application/json content type. The consumer server should respond with a 200 HTTP status code. If the consumer was unable to handle the webhook, the request will be retried every 10 minutes but not more than 5 times.
 
 #### Body data
 
-All web-hook requests are performing with
+All webhook requests are performed with
 
 ```json
 {
@@ -86,12 +86,12 @@ All web-hook requests are performing with
 
 #### Request headers
 
-Also, all request contains additional data in headers:
+Also, all requests contain additional data in headers:
 
 1. `'Content-type': 'application/json'`
 2. `'X-TXC-APIKEY': api_key` - the WhiteBIT webhook API key
-3. `'X-TXC-PAYLOAD': payload'` - where payload is base64-encoded body data
-4. `'X-TXC-SIGNATURE': signature` - where signature is `hex(HMAC_SHA512(payload), key=api_secret))`
+3. `'X-TXC-PAYLOAD': payload` - where payload is base64-encoded body data
+4. `'X-TXC-SIGNATURE': signature` - where signature is `hex(HMAC_SHA512(payload), key=api_secret)`
 
 On the consumer side, process the security headers to verify the request originated from WhiteBIT.
 
@@ -143,7 +143,7 @@ Performed when deposit was accepted. Request example:
 }
 ```
 
-Performed when deposit was update. Request example:
+Performed when deposit was updated. Request example:
 
 ```json
 {