DOCCORE-199 Some small fixes across pages (#2910) (#2917)

1. Fix the broken link to the Github repo
2. Fix the cross-reference
3. Remove labels 'Introduced in 5.x'

Author: NataliaIvakina

modules/ROOT/pages/cloud-deployments/neo4j-aws.adoc

@@ -24,7 +24,7 @@ The  CloudFormation template always installs the latest available version.
 
 AWS CloudFormation is a declarative Infrastructure as Code (IaC) language that is based on YAML and instructs AWS to deploy a set of cloud resources.
 
-The Neo4j CloudFormation template's code is available on link:https://github.com/neo4j-partners/amazon-cloud-formation-neo4j/blob/main/neo4j.template.yaml[GitHub].
+The Neo4j CloudFormation template's code is available on link:https://github.com/neo4j-partners/amazon-cloud-formation-neo4j/blob/main/ee/neo4j-ee.template.yaml[GitHub].
 It takes several parameters as inputs, deploys a set of cloud resources, and provides outputs that can be used to connect to a Neo4j DBMS.
 
 === Important considerations
@@ -308,4 +308,4 @@ To obtain a valid license for either Neo4j, Bloom, or GDS, reach out to your Neo
 == Delete CloudFormation Stack and destroy resources
 
 Select the CloudFormation stack to be removed and click the *Delete* button.
-The stack deletion cleans up all AWS resources deployed by it.
+The stack deletion cleans up all AWS resources deployed by it.

modules/ROOT/pages/docker/docker-compose-standalone.adoc

@@ -1,5 +1,5 @@
 :description: Running Neo4j in a Docker container using Docker Compose
-:page-role: new-5.24
+
 [[docker-compose-neo4j-standalone]]
 = Deploy a Neo4j standalone server using Docker Compose
 

modules/ROOT/pages/monitoring/logging.adoc

@@ -906,7 +906,7 @@ To get that capability, set xref:configuration/configuration-settings.adoc#confi
 | `false`
 a|
 If `true`, obfuscates all error information that can contain sensitive data before writing it to the log.
-This applies to error messages when the query log uses pattern layout or xref:#_use_json_format_for_the_query_log[JSON layout] with fields such as `failureReason` and `statusDescription`, where `statusDescription` is an element of `errorInfo`.
+This applies to error messages when the query log uses pattern layout or <<#_use_json_format_for_the_query_log,JSON layout>> with fields such as `failureReason` and `statusDescription`, where `statusDescription` is an element of `errorInfo`.
 
 It is recommended to set this setting to `true` in production.
 

modules/ROOT/pages/security/ssl-fips-compatibility.adoc

@@ -2,7 +2,7 @@
 = Configuring SSL for FIPS 140-2 compatibility
 :description: How to configure Neo4j to use FIPS compatible SSL encryption.
 :keywords: ssl, tls, authentication, encryption, encrypted, security, fips, fips 140, fips 140-2, nist, hipaa
-:page-role: enterprise-edition new-5.24
+:page-role: enterprise-edition
 
 Federal Information Processing Standards (FIPS) 140 is a U.S. government standard established by the National Institute of Standards and Technology (NIST) which is used to accredit cryptographic modules such as those used in TLS network encryption.
 While FIPS 140 compliance is primarily required for federal agencies and their contractors, it also is used in the healthcare sector under regulations like the Health Insurance Portability and Accountability Act (HIPAA) to protect patient data.