DOCS-14440 Update getlast.error in replica set config command REMOVED

Author: ianf-mongodb

source/includes/5.0-changes-getLastErrorDefaults-removed.rst

@@ -0,0 +1,5 @@
+Starting in MongoDB 5.0, you cannot specify a default write concern with
+:rsconf:`settings.getLastErrorDefaults` other than the default of 
+``{ w: 1, wtimeout: 0 }`` . Instead, use the 
+:dbcommand:`setDefaultRWConcern` command to set the default read or
+write concern configuration for a replica set or sharded cluster.

source/reference/replica-configuration.txt

@@ -483,19 +483,11 @@ Replica Set Configuration Fields
 
       *Type*: document
 
-      A document that specifies the :doc:`write concern
-      </core/replica-set-write-concern>` for the replica set. The
-      replica set will use this write concern only when :ref:`write
-      operations <write-methods-incompatibility>` or
-      :dbcommand:`getLastError` specify no other write concern.
-
-      If :rsconf:`settings.getLastErrorDefaults` is
-      not set, the default write concern for the replica set only
-      requires confirmation from the primary.
+      Unavailable starting in MongoDB 5.0
 
       .. important::
 
-         .. include:: /includes/extracts/4.4-changes-getLastErrorDefaults-deprecation.rst
+         .. include:: /includes/5.0-changes-getLastErrorDefaults-removed.rst
 
    .. rsconf::  settings.getLastErrorModes
 

source/release-notes/5.0.txt

@@ -357,6 +357,11 @@ Starting in MongoDB 5.0, these database commands and
 Replica Sets
 ------------
 
+Removed Customizable Values For getLastErrorDefaults 
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+.. include:: /includes/5.0-changes-getLastErrorDefaults-removed.rst
+
 ``hello`` Command
 ~~~~~~~~~~~~~~~~~