Apply suggestions from @mjmartineau

Co-authored-by: Mat Martineau <[email protected]>

faq.md

@@ -156,8 +156,8 @@ defined:
 
 ## How to check if MPTCP is working?
 
-The easiest way is to check with a special test server than will if MPTCP is
-being used, and will return the info to the client, e.g.
+The easiest way is to check with a special test server that will confirm MPTCP is
+being used and return that info to the client, e.g.
 ```bash
 $ mptcpize run curl http://test.multipath-tcp.org:5000
 You are using MPTCP.
@@ -185,16 +185,16 @@ page.
 
 ## High number of retransmissions / dropped packets at the NIX RX queue level?
 
-Even if with MPTCP, the subflow processing is done by the TCP stack, the main
+Even with MPTCP, subflow processing is done by the TCP stack. The main
 difference with plain TCP is that this processing does not use the socket
 backlog and always happens in second-level interrupt handlers called
 [*bottom half*](https://en.wikipedia.org/wiki/Interrupt_handler) (BH) in Linux.
 When the host is under heavy load, BH processing happens in `ksoftirqd` context,
 and there is some latency between the `ksoftirqd` scheduling and the moment
-`ksoftirqd` actually runs that. This depends on the process scheduler decisions
+`ksoftirqd` actually runs the handler. This depends on process scheduler decisions
 (and settings).
 
-A way to reduce these retransmissions and avoid the dropped packets at the NIC
+A way to reduce these retransmissions and avoid dropped packets at the NIC
 level is to increase the NIC RX queue. See issue
 [#253](https://github.com/multipath-tcp/mptcp_net-next/issues/253) for more
 details.