Make legacy API and its deprecation more prominent

Author: gjmwoods

modules/ROOT/pages/actions/begin-and-commit-a-transaction-in-one-request.adoc

@@ -51,56 +51,3 @@ _Example response_
 ----
 
 
-== Legacy Endpoints label:deprecated[]
-
-[IMPORTANT]
-====
-The API described in this section of the manual has been deprecated and will be removed in Neo4j 5.0.
-====
-
-Starting with Neo4j version 4.3, statements submitted via these endpoints will be processed by the user's respective _home database_.
-Previous versions rely on the the globally configured _default database_.
-
-_Example request_
-
-* *+POST+* +http://localhost:7474/db/neo4j/tx/commit+
-* *+Accept:+* +application/json;charset=UTF-8+
-* *+Content-Type:+* +application/json+
-
-[source, JSON, role="nocopy"]
-----
-{
-  "statements": [
-    {
-      "statement": "MATCH (n) WHERE id(n) = $nodeId RETURN n",
-      "parameters": {
-        "nodeId": 2
-      }
-    }
-  ]
-}
-----
-
-_Example response_
-
-* *+200:+* +OK+
-* *+Content-Type:+* +application/json;charset=utf-8+
-
-[source, JSON, role="nocopy"]
-----
-{
-  "results" : [ {
-    "columns" : [ "n" ],
-    "data" : [ {
-      "row" : [ { } ],
-      "meta" : [ {
-        "id" : 2,
-        "type" : "node",
-        "deleted" : false
-      } ]
-    } ]
-  } ],
-  "errors" : [ ]
-}
-----
-

modules/ROOT/pages/actions/index.adoc

@@ -21,6 +21,7 @@ There are several _actions_ that can be performed using the Cypher transaction H
 * xref:actions/commit-an-open-transaction.adoc[]
 * xref:actions/rollback-an-open-transaction.adoc[]
 * xref:actions/begin-and-commit-a-transaction-in-one-request.adoc[]
+* xref:actions/legacy-endpoints.adoc[]
 
 *Additional actions:*
 

modules/ROOT/pages/actions/legacy-endpoints.adoc

@@ -0,0 +1,65 @@
+:description: Legacy endpoints.
+
+[[http-api-legacy-endpoints]]
+= Legacy Endpoints label:deprecated[]
+
+[IMPORTANT]
+====
+The API described in this section of the manual has been deprecated and will be removed in Neo4j 5.0.
+====
+
+For backwards compatibility with neo4j 3.5, it is still possible to
+use the HTTP API without specifying the database in the URL. For example:
+
+`http://localhost:7474/db/data/transaction/commit`.
+
+Since the database is not specified, the statements will be executed against the user's _home database_.
+
+All endpoints in this manual can also be executed against the legacy API where `db/<database-name>` is replaced with `db/data/transaction`. The input format and output formata are identical for both the legacy API and the current API.
+
+For example beginning and commiting a transaction in a single requests looks as follows:
+
+_Example request_
+
+* *+POST+* +http://localhost:7474/db/data/transaction/commit+
+* *+Accept:+* +application/json;charset=UTF-8+
+* *+Content-Type:+* +application/json+
+
+[source, JSON, role="nocopy"]
+----
+{
+  "statements": [
+    {
+      "statement": "MATCH (n) WHERE id(n) = $nodeId RETURN n",
+      "parameters": {
+        "nodeId": 2
+      }
+    }
+  ]
+}
+----
+
+_Example response_
+
+* *+200:+* +OK+
+* *+Content-Type:+* +application/json;charset=utf-8+
+
+[source, JSON, role="nocopy"]
+----
+{
+  "results" : [ {
+    "columns" : [ "n" ],
+    "data" : [ {
+      "row" : [ { } ],
+      "meta" : [ {
+        "id" : 2,
+        "type" : "node",
+        "deleted" : false
+      } ]
+    } ]
+  } ],
+  "errors" : [ ]
+}
+----
+
+