diff --git a/src/docs/build-deploy-and-maintain-apps/setup-artifactory-project-repository.md b/src/docs/build-deploy-and-maintain-apps/setup-artifactory-project-repository.md
index 8e4c198..712dc55 100644
--- a/src/docs/build-deploy-and-maintain-apps/setup-artifactory-project-repository.md
+++ b/src/docs/build-deploy-and-maintain-apps/setup-artifactory-project-repository.md
@@ -157,7 +157,6 @@ This creates a local repository in your Artifactory Project. Within the next 10
 
 * [Archeobot](https://github.com/bcgov/platform-services-archeobot)
 * [Artifactory](https://artifacts.developer.gov.bc.ca)
-* [Just Ask! tool](https://just-ask.developer.gov.bc.ca/)
 * [Setup an Artifactory service account](../build-deploy-and-maintain-apps/setup-artifactory-service-account.md)
 
 
diff --git a/src/docs/build-deploy-and-maintain-apps/setup-artifactory-service-account.md b/src/docs/build-deploy-and-maintain-apps/setup-artifactory-service-account.md
index f187c4e..88b8377 100644
--- a/src/docs/build-deploy-and-maintain-apps/setup-artifactory-service-account.md
+++ b/src/docs/build-deploy-and-maintain-apps/setup-artifactory-service-account.md
@@ -90,7 +90,6 @@ Keep in mind that this is a _new_ account, and that you will need to re-add this
 
 * [Archeobot](https://github.com/bcgov/platform-services-archeobot)
 * [Artifactory](https://artifacts.developer.gov.bc.ca)
-* [Just Ask! tool](https://just-ask.developer.gov.bc.ca/)
 * [Setup an Artifactory project and repository](../build-deploy-and-maintain-apps/setup-artifactory-project-repository.md)
 
 
diff --git a/src/docs/database-and-api-management/high-availability-database-clusters.md b/src/docs/database-and-api-management/high-availability-database-clusters.md
index 028e994..91c077b 100644
--- a/src/docs/database-and-api-management/high-availability-database-clusters.md
+++ b/src/docs/database-and-api-management/high-availability-database-clusters.md
@@ -45,6 +45,7 @@ Highly-available database clusters meet both of these requirements. Each databas
 If the primary instance goes down, the secondary instances will elect a new primary right away. When another pod spins up to take the place of the original failed primary, it will join the cluster as a new secondary instance. This election process is usually fast enough to be unnoticeable.
 
 So, what does this mean for your software architecture?
+
 * Since HA clusters require 3 pods and each pod needs its own copy of the database, your storage requirements will be triple the size of your database. 
 * The primary instance will have more load than the secondary instances. Since any member of the cluster can be elected as primary, you need provide all instances with enough compute resources to act as the primary instance.
 * Your application must be able to handle connecting to a new instance at any time.
diff --git a/src/docs/security-and-privacy-compliance/platform-security-compliance.md b/src/docs/security-and-privacy-compliance/platform-security-compliance.md
index 738dcaa..c567472 100644
--- a/src/docs/security-and-privacy-compliance/platform-security-compliance.md
+++ b/src/docs/security-and-privacy-compliance/platform-security-compliance.md
@@ -113,7 +113,6 @@ Many of the platform tools have **completed** security assessments.  These inclu
 * KeyCloak Common Host Single Sign-on
 * Artifactory
 * Sysdig Monitor
-* Just Ask!
 * Certbot
 * MS Teams
 * Vault