update deployment center

modules/ROOT/pages/addition/agent-installation/agent-install.adoc

@@ -1,12 +1,12 @@
 = Install agent
 
-* Download platform specific binary: https://neo4j.com/download-center/#ops-manager[Download]
+* Download platform specific binary: https://neo4j.com/deployment-center/?ops-manager[Download]
 +
 [NOTE]
-==== 
+====
 In certain environments, downloading agents is not an option.
 Therefore, NOM agent binaries are also bundled with Neo4j packages.
-NOM agent packages can be found in the `products` folder in the Neo4j home directory. 
+NOM agent packages can be found in the `products` folder in the Neo4j home directory.
 These binaries have support for the Neo4j version that they are bundled with.
 ====
 

modules/ROOT/pages/first-look/linux-first-look.adoc

@@ -9,7 +9,7 @@ NOTE: The query log feature is only available for DBMSs with instances that are
 == Create persistence DBMS
 
 === Download and extract
-Download latest Neo4j Linux/Mac executable from https://neo4j.com/download-center/#current-releases[here] and extract the package.
+Download latest Neo4j Linux/Mac executable from https://neo4j.com/deployement-center/?current-releases[here] and extract the package.
 Extracted directory location is referred to as NEO4J_HOME form now on.
 
 === Change password

modules/ROOT/pages/installation/kubernetes/helm-charts.adoc

@@ -9,7 +9,7 @@
 - Access to a Kubernetes enviroment (cloud, on-prem, or local with a `LoadBalancer` resource implementation).
 
 == NOM server Helm Chart
-* Download the NOM server Helm Chart from link:https://neo4j.com/download-center/#ops-manager[Neo4j Download Center].
+* Download the NOM server Helm Chart from link:https://neo4j.com/deployment-center/?ops-manager[Neo4j Deployment Center].
 
 * Following is the reference `values.yaml` for NOM server Helm Chart:
 ----
@@ -201,7 +201,7 @@ Following is an example values snippet that demonstrates this usecase with inlin
 ----
 secretsFromSecrets:
   storageUri:
-    secretName: "secret1" 
+    secretName: "secret1"
     key: "uri"
   storageUsername:
     secretName: "secret2"

modules/ROOT/pages/installation/server.adoc

@@ -8,10 +8,10 @@ The second step is to download and configure arguments and/or environment variab
 Both ways are described below.
 Running as a service is the recommended way of operating the NOM Server.
 
-Releases of Neo4j enterprise all come bundled with the most current version of NOM at the time of that Neo4j release. 
+Releases of Neo4j enterprise all come bundled with the most current version of NOM at the time of that Neo4j release.
 Please note that this does not have to be the most current version of NOM.
 You can find NOM as `.zip` or `.tar.gz` inside your Neo4j folder under `/products`.
-Alternatively, you can download any version of the NOM Server, including the agent binaries here: https://neo4j.com/download-center/#ops-manager[Download].
+Alternatively, you can download any version of the NOM Server, including the agent binaries here: https://neo4j.com/deployment-center/?ops-manager[Download].
 In any case, please extract the content from the downloaded `.zip` or `.tar.gz` file to whichever directory you want to operate NOM from
 (in the following referenced as NOM server-folder).
 
@@ -58,7 +58,7 @@ This file includes a section that needs to be adjusted to your environment (e.g.
 
 As an alternative to changing the arguments in the `neo4j-ops-manager-server.service` file, you can instead use environment variables to achieve the same result.
 The `neo4j-ops-manager-server.service` file contains the necessary information for this.
-The table <<config_ref,here>> contains environment variables and example values. 
+The table <<config_ref,here>> contains environment variables and example values.
 
 ==== Installation
 
@@ -94,7 +94,7 @@ sudo systemctl stop neo4j-ops-manager-server
 ====
 *For SELinux*
 
-The SELinux context of the server binary must be changed so that it can be executed from the service. 
+The SELinux context of the server binary must be changed so that it can be executed from the service.
 To permanently change the SELinux context of the file, run the following commands:
 [source, terminal, role=noheader]
 ----