SERVER-84800: Remove eMRC:false in non-repl code (#23020)

GitOrigin-RevId: 0e5eaf9533ac9bf0d4d06f5e37eccf660cf3a5f1

debian/mongod.1

@@ -1908,33 +1908,6 @@ persist the changes made using \fBreplSetResizeOplog\f1\f1
 through a restart, update the value of
 \fB\-\-oplogMinRetentionHours\f1\f1\&.
 .RE
-.PP
-\fBmongod \-\-enableMajorityReadConcern\f1
-.RS
-.PP
-\fIDefault\f1: true
-.PP
-Configures support for \fB"majority"\f1\f1 read concern.
-.PP
-Starting in MongoDB 5.0,
-\fB\-\-enableMajorityReadConcern\f1\f1 cannot be changed
-and is always set to \fBtrue\f1\&. In earlier versions of MongoDB,
-\fB\-\-enableMajorityReadConcern\f1\f1 was configurable.
-.PP
-If you are using a three\-member primary\-secondary\-arbiter (PSA)
-architecture, consider the following:
-.RS
-.IP \(bu 2
-The write concern \fB"majority"\f1\f1 can cause
-performance issues if a secondary is unavailable or lagging. For
-advice on how to mitigate these issues, see
-\fBMitigate Performance Issues with PSA Replica Set\f1\&.
-.IP \(bu 2
-If you are using a global default \fB"majority"\f1\f1
-and the write concern is less than the size of the majority,
-your queries may return stale (not fully replicated) data.
-.RE
-.RE
 .SS SHARDED CLUSTER OPTIONS
 .PP
 \fBmongod \-\-configsvr\f1