remove the rest of core and rr

modules/ROOT/pages/authentication-authorization/password-and-user-recovery.adoc

@@ -98,7 +98,7 @@ You can use a client such as xref:tools/cypher-shell.adoc[Cypher Shell] or the N
 
 [NOTE]
 ====
-In a cluster deployment, you should complete the steps only on one of the Core servers.
+In a cluster deployment, you should complete the steps only on one of the cluster members.
 ====
 
 . Complete the steps in xref:authentication-authorization/password-and-user-recovery.adoc#disable-authentication[Disable authentication] as per your deployment.
@@ -112,7 +112,7 @@ $ bin/cypher-shell -d system
 +
 [NOTE]
 ====
-label:Cluster[] If you have specified a non-default port for your `bolt` connector, add `-a neo4j://<your-core>:<non-default-bolt-port>` to the `cypher-shell` command to be able to connect to your Core server.
+label:Cluster[] If you have specified a non-default port for your `bolt` connector, add `-a neo4j://<your-cluster-member>:<non-default-bolt-port>` to the `cypher-shell` command to be able to connect to your cluster member.
 ====
 . Set a new password for the admin user.
 In this example, the admin user is named `neo4j`.
@@ -136,7 +136,7 @@ You can use a client such as xref:tools/cypher-shell.adoc[Cypher Shell] or the N
 
 [NOTE]
 ====
-In a cluster deployment, you should complete the steps only on one of the Core servers.
+In a cluster deployment, you should complete the steps only on one of the cluster members.
 ====
 
 . Complete the steps in xref:authentication-authorization/password-and-user-recovery.adoc#disable-authentication[Disable authentication] as per your deployment.
@@ -150,7 +150,7 @@ $ bin/cypher-shell -d system
 +
 [NOTE]
 ====
-label:Cluster[] If you have specified a non-default port for your `bolt` connector, add `-a neo4j://<your-core>:<non-default-bolt-port>` to the `cypher-shell` command to be able to connect to your Core server.
+label:Cluster[] If you have specified a non-default port for your `bolt` connector, add `-a neo4j://<your-clustder-member>:<non-default-bolt-port>` to the `cypher-shell` command to be able to connect to your cluster member.
 ====
 . Grant the admin user role to an existing user.
 In this example, the user is named `neo4j`.
@@ -174,7 +174,7 @@ If you have removed the admin role from your system entirely, you can use a clie
 
 [NOTE]
 ====
-In a cluster deployment, you should complete the steps only on one of the Core servers.
+In a cluster deployment, you should complete the steps only on one of the cluster members.
 ====
 
 . Complete the steps in xref:authentication-authorization/password-and-user-recovery.adoc#disable-authentication[Disable authentication] as per your deployment.
@@ -188,7 +188,7 @@ $ bin/cypher-shell -d system
 +
 [NOTE]
 ====
-label:Cluster[] If you have specified a non-default port for your `bolt` connector, add `-a neo4j://<your-core>:<non-default-bolt-port>` to the `cypher-shell` command to be able to connect to your Core server.
+label:Cluster[] If you have specified a non-default port for your `bolt` connector, add `-a neo4j://<your-cluster-member>:<non-default-bolt-port>` to the `cypher-shell` command to be able to connect to your cluster member.
 ====
 . Recreate the admin role with its original capabilities.
 +
@@ -244,15 +244,15 @@ $ bin/neo4j start
 ======
 [.include-with-cluster]
 ======
-. Stop the Core servers.
+. Stop the cluster members.
 +
 [source, shell]
 ----
 $ bin/neo4j stop
 ----
 +
-. Enable the authentication and restore each Core server to its original configuration (See xref:configuration/password-and-user-recovery.adoc#disable-authentication[Disable authentication]).
-. Start the cluster (all Core servers and Read Replicas):
+. Enable the authentication and restore each cluster member to its original configuration (See xref:configuration/password-and-user-recovery.adoc#disable-authentication[Disable authentication]).
+. Start the cluster (all cluster members:
 +
 [source, shell]
 ----