Fix cloud URIs (#2195) (#2198)

Author: NataliaIvakina

modules/ROOT/pages/clustering/databases.adoc

@@ -304,7 +304,7 @@ See <<cluster-seed-uri, Seed from URI>> for more details.
 
 [source, shell]
 ----
-CALL dbms.cluster.recreateDatabase("neo4j", {seedURI: "s3:/myBucket/myBackup.backup"});
+CALL dbms.cluster.recreateDatabase("neo4j", {seedURI: "s3://myBucket/myBackup.backup"});
 ----
 
 [[seed-servers]]
@@ -351,7 +351,7 @@ This means the store is replaced by the most up-to-date seeder if available; oth
 +
 [source, shell]
 ----
-CALL dbms.cluster.recreateDatabase("neo4j", {seedingServers: [], seedURI: "s3:/myBucket/myBackup.backup"});
+CALL dbms.cluster.recreateDatabase("neo4j", {seedingServers: [], seedURI: "s3://myBucket/myBackup.backup"});
 ----
 
 [[alter-topology-recreate]]
@@ -537,7 +537,7 @@ include::partial$/aws-s3-credentials.adoc[]
 +
 [source,shell, role="nocopy"]
 ----
-CREATE DATABASE foo OPTIONS { existingData: 'use', seedURI: 's3:/myBucket/myBackup.backup' }
+CREATE DATABASE foo OPTIONS { existingData: 'use', seedURI: 's3://myBucket/myBackup.backup' }
 ----
 
 ======
@@ -550,7 +550,7 @@ include::partial$/gcs-credentials.adoc[]
 +
 [source,shell]
 ----
-CREATE DATABASE foo OPTIONS { existingData: 'use', seedURI: 'gs:/myBucket/myBackup.backup' }
+CREATE DATABASE foo OPTIONS { existingData: 'use', seedURI: 'gs://myBucket/myBackup.backup' }
 ----
 ======
 [role=include-with-Azure-cloud-storage]
@@ -576,7 +576,7 @@ To seed up to a specific date, you need to pass the differential backup, which c
 +
 [source,shell]
 ----
-CREATE DATABASE foo OPTIONS { existingData: 'use', seedURI: 's3:/myBucket/myBackup.backup', seedRestoreUntil: datetime("2019-06-01T18:40:32.142+0100") }
+CREATE DATABASE foo OPTIONS { existingData: 'use', seedURI: 's3://myBucket/myBackup.backup', seedRestoreUntil: datetime("2019-06-01T18:40:32.142+0100") }
 ----
 +
 This will seed the database with transactions committed before the provided timestamp.
@@ -588,7 +588,7 @@ To seed up to a specific transaction ID, you need to pass the differential backu
 +
 [source,shell]
 ----
-CREATE DATABASE foo OPTIONS { existingData: 'use', seedURI: 's3:/myBucket/myBackup.backup', seedRestoreUntil: 123 }
+CREATE DATABASE foo OPTIONS { existingData: 'use', seedURI: 's3://myBucket/myBackup.backup', seedRestoreUntil: 123 }
 ----
 +
 This will seed the database with transactions up to, but not including transaction 123.
@@ -617,7 +617,7 @@ Each configuration value is specified as a name followed by `=` and the value, a
 
 [source, cypher, role="noplay"]
 ----
-CREATE DATABASE foo OPTIONS { existingData: 'use', seedURI: 's3:/myBucket/myBackup.backup', seedConfig: 'region=eu-west-1' }
+CREATE DATABASE foo OPTIONS { existingData: 'use', seedURI: 's3://myBucket/myBackup.backup', seedConfig: 'region=eu-west-1' }
 ----
 
 `S3SeedProvider` also requires passing in credentials.
@@ -629,7 +629,7 @@ If this configuration is not performed, the `seedCredentials` option fails.
 
 [source, cypher, role="noplay"]
 ----
-CREATE DATABASE foo OPTIONS { existingData: 'use', seedURI: 's3:/myBucket/myBackup.backup', seedConfig: 'region=eu-west-1', seedCredentials: [accessKey];[secretKey] }
+CREATE DATABASE foo OPTIONS { existingData: 'use', seedURI: 's3://myBucket/myBackup.backup', seedConfig: 'region=eu-west-1', seedCredentials: [accessKey];[secretKey] }
 ----
 Where `accessKey` and `secretKey` are provided by AWS.
 
@@ -643,11 +643,11 @@ Where `accessKey` and `secretKey` are provided by AWS.
 
 | `file:`
 | `FileSeedProvider`
-| `file:/tmp/backup1.backup`
+| `file://tmp/backup1.backup`
 
 | `ftp:`
 | `URLConnectionSeedProvider`
-| `ftp:://myftp.com/backups/backup1.backup`
+| `ftp://myftp.com/backups/backup1.backup`
 
 | `http:`
 | `URLConnectionSeedProvider`