removed flutterwave style test

Author: Dekunledev

CHANGELOG.md

@@ -7,6 +7,7 @@
 - Enhanced success status check logic to handle different status values ("success" and "completed").
 - Improved error handling and state management.
 - Removed deprecated components: `flutterwave_style.dart` and `standard_webview.dart`.
+- Removed `flutterwave_style_test.dart`.
 - Updated the SDK requirements to `>=2.17.0`.
 - Upgraded dependencies to the latest versions.
 - Removed unused dependencies: webview_flutter, modal_bottom_sheet and uuid.

README.md

@@ -92,7 +92,7 @@ Call the verify transaction [endpoint](https://developer.flutterwave.com/docs/tr
 #### Note
 
 - `ChargeResponse` can be null, depending on if the user cancels the transaction by pressing back.
-- You need to confirm the transaction is successful. Ensure that the txRef, amount, and status are correct and successful. Be sure to [verify the transaction details](https://developer.flutterwave.com/docs/transaction-verification) before providing value.
+- You need to confirm the transaction status is successful. Ensure that the txRef, amount, and status are correct and successful. Be sure to [verify the transaction details](https://developer.flutterwave.com/docs/transaction-verification) before providing value.
 - Some payment methods are not instant, such a `Pay with Bank Transfers, Pay with Bank`, and so you would need to rely on [webhooks](https://developer.flutterwave.com/docs/webhooks) or call the transaction verification service using the [`transactionId`](https://developer.flutterwave.com/reference/verify-transaction), or transaction reference you created(`txRef`)
 - For such long payments like the above, closing the payment page returns a `cancelled` status, so your final source of truth has to be calling the transaction verification service.