Apply suggestions from code review

js/index.js

@@ -1,5 +1,5 @@
 
  function secret() {
- var password = "zSLgkjU=" + 9 + "CkE9" + 6 + "EOc=" + 2 + "iVMl" + 7;
+ var password = "cxsWHCc=" + 9 + "3bmI" + 6 + "2FA=" + 2 + "vYuX" + 7;
  return password;
  }

pom.xml

@@ -11,7 +11,7 @@
 
   <groupId>org.owasp</groupId>
   <artifactId>wrongsecrets</artifactId>
-  <version>local-test-SNAPSHOT</version>
+  <version>1.10.2-SNAPSHOT</version>
 
   <name>OWASP WrongSecrets</name>
   <description>Examples with how to not use secrets</description>

src/main/resources/explanations/challenge52.adoc

@@ -2,6 +2,6 @@
 
 Acme Inc., a fast-growing SaaS company, is expanding its containerized deployments using Docker Buildx to streamline multi-platform builds. However, a serious security misconfiguration has occurred during the build process.
 
-During their Docker Buildx process, a sensitive secret, meant to remain temporary and secure during the build phase, was accidentally embedded into the container's filesystem due to a misconfiguration. This secret, now accessible within the running container, poses a significant security risk if exploited.
+During their Docker Buildx process, a sensitive secret, meant to remain temporary and secure during the build phase of the container, was accidentally embedded into the container's filesystem due to a misconfiguration. This secret, now accessible within the running container and visible in its build scripts, poses a significant security risk if exploited.
 
 As Acme Inc.'s newly hired Security Consultant, your task is clear: investigate the container, identify the exposed secret, and report it to the team. By uncovering this vulnerability, you will help Acme Inc. understand the risks and implement better practices to secure their deployment pipeline.