DRIVERS-3439 remove more pre-4.2 references found in review

Author: jyemin

source/find_getmore_killcursors_commands/find_getmore_killcursors_commands.md

@@ -27,8 +27,7 @@ A BSON document containing the fields making up a MongoDB server command.
 
 #### Wire Protocol
 
-The binary protocol used to talk with MongoDB over a socket. It's made up by the OP_QUERY, OP_GET_MORE, OP_KILL_CURSORS,
-OP_INSERT, OP_UPDATE and OP_DELETE.
+The binary protocol used to talk with MongoDB over a socket.
 
 ## Guidance
 
@@ -49,8 +48,7 @@ Drivers:
 ### find
 
 The [find](https://www.mongodb.com/docs/manual/reference/command/find/) command replaces the query functionality of the
-OP_QUERY wire protocol message but cannot execute queries against special collections. Unlike the legacy OP_QUERY wire
-protocol message, the **find** command cannot be used to execute other commands.
+OP_QUERY wire protocol message but cannot execute queries against special collections.
 
 For a successful command, the document returned from the server has the following format:
 
@@ -180,16 +178,15 @@ Further, after these transformation:
 
 #### BatchSize of 1
 
-In 3.2 a batchSize of 1 means return a single document for the find command and it will not destroy the cursor after the
-first batch of documents are returned. Given a query returning 4 documents the number of commands issues will be.
+A batchSize of 1 means return a single document for the find command and it will not destroy the cursor after the first
+batch of documents are returned. Given a query returning 4 documents the number of commands issues will be.
 
 1. **find** command with batchSize=1
 2. **getMore** command with batchSize=1
 3. **getMore** command with batchSize=1
 4. **getMore** command with batchSize=1
 
-The driver **SHOULD NOT attempt to emulate the behavior seen in 3.0 or earlier** as the new find command enables the
-user expected behavior of allowing the first result to contain a single document when specifying batchSize=1.
+The `find` command allows the first result to contain a single document when specifying batchSize=1.
 
 #### Tailable cursors
 
@@ -242,8 +239,8 @@ to the value of the option **maxAwaitTimeMS**. If no **maxAwaitTimeMS** is speci
 ### getMore
 
 The [getMore](https://www.mongodb.com/docs/manual/reference/command/getMore/) command replaces the **OP_GET_MORE** wire
-protocol message. The query flags passed to OP_QUERY for a getMore command MUST be secondaryOk=true when sent to a
-secondary. The OP_QUERY namespace MUST be the same as for the **find** and **killCursors** commands.
+protocol message. The query flags passed to OP_MSG for a getMore command MUST be secondaryOk=true when sent to a
+secondary. The OP_MSG namespace MUST be the same as for the **find** and **killCursors** commands.
 
 ```typescript
 interface GetMoreCommand {
@@ -296,8 +293,8 @@ The driver's local cursor MUST update its `id` and `ns`, as well as store the `n
 ### killCursors
 
 The [killCursors](https://www.mongodb.com/docs/manual/reference/command/killCursors/) command replaces the
-**OP_KILL_CURSORS** wire protocol message. The OP_QUERY namespace MUST be the same as for the **find** and **getMore**
-commands. The **killCursors** command is optional to implement in **MongoDB 3.2**.
+**OP_KILL_CURSORS** wire protocol message. The OP_MSG namespace MUST be the same as for the **find** and **getMore**
+commands.
 
 The command response will be as follows:
 
@@ -407,11 +404,6 @@ Like other commands, the find and getMore commands will not use the OP_REPLY res
 
 ## FAQ
 
-### Changes in error handling for 3.2 tailable cursor
-
-Tailable cursors pointing to documents in a capped collection that get overwritten will return a zero document result in
-MongoDB 3.0 or earlier but will return an error in MongoDB 3.2
-
 ### Explain command
 
 There is no equivalent of the `$explain` modifier in the find command. The driver SHOULD use the **explain** command.

source/server-discovery-and-monitoring/server-discovery-and-monitoring.md

@@ -1582,15 +1582,8 @@ drivers continue to maintain the reversed logic when connected to a topology tha
 
 #### Requirements for read-your-writes consistency
 
-Using (electionId, setVersion) only provides read-your-writes consistency if:
-
-- The application uses the same MongoClient instance for write-concern "majority" writes and read-preference "primary"
-    reads, and
-- All members use MongoDB 2.6.10+, 3.0.0+ or 3.2.0+ with replication protocol 0 and clocks are *less* than 30 seconds
-    skewed, or
-- All members run MongoDB 3.2.0 and replication protocol 1 and clocks are *less* skewed than the election timeout
-    (`electionTimeoutMillis`, which defaults to 10 seconds), or
-- All members run MongoDB 3.2.1+ and replication protocol 1 (in which case clocks need not be synchronized).
+Using (electionId, setVersion) only provides read-your-writes consistency if the application uses the same MongoClient
+instance for write-concern "majority" writes and read-preference "primary" reads.
 
 #### Scenario
 

source/unified-test-format/unified-test-format.md

@@ -3187,7 +3187,6 @@ The test runner MAY ignore the following command failures:
 
 - Interrupted(11601) to work around [SERVER-38335](https://jira.mongodb.org/browse/SERVER-38335).
 - Unauthorized(13) to work around [SERVER-54216](https://jira.mongodb.org/browse/SERVER-54216).
-- CommandNotFound(59) if the command is executed on a pre-3.6 server
 
 Note that Atlas, by design, does not allow database users to kill sessions belonging to other users. This makes it
 impossible to guarantee that an existing transaction will not block test execution. To work around this, test runners