removed redacted parts

.github/workflows/pages.yaml

@@ -31,7 +31,7 @@ jobs:
   build:
     runs-on: ubuntu-latest
     env:
-      HUGO_VERSION: 0.126.3
+      HUGO_VERSION: 0.127.O
     steps:
       - name: Checkout
         uses: actions/checkout@v4

content/samples/concept.md

@@ -7,59 +7,59 @@ weight: 200
 
 ##  Main concepts
 
-### What is \[PRODUCT\]
-The \[PRODUCT\] solution is an \[REDACTED\] application with a monitoring Web interface.
-The \[PRODUCT\] process is fully integrated with the \[REDACTED\] deployments: the distribution macro-commands call the \[PRODUCT\] functions. Execute the macro-commands in \[REDACTED\] and monitor the results in the \[PRODUCT\] Web App.
+### What is DROPS WAP
+The DROPS WAP solution is an ARCAD application with a monitoring Web interface.
+The DROPS WAP process is fully integrated with the ARCAD deployments: the distribution macro-commands call the DROPS WAP functions. Execute the macro-commands in ARCAD and monitor the results in the DROPS WAP Web App.
 
-### How \[PRODUCT\] works
+### How DROPS WAP works
 
-\[REDACTED\] application variables are used to control if \[PRODUCT\] is proposed when distributing a release to a target site.​  
+ARCAD application variables are used to control if DROPS WAP is proposed when distributing a release to a target site.​  
 
-The standard \[REDACTED\] macro-command (DISTRIB) starts and ends the \[PRODUCT\] replication and synchronization process. The progress of the replication and synchronization is monitored with the \[PRODUCT\] Web Studio.​
+The standard ARCAD macro-command (DISTRIB) starts and ends the DROPS WAP replication and synchronization process. The progress of the replication and synchronization is monitored with the DROPS WAP Web Studio.​
 
-Files under \[PRODUCT\] pass through two stages: replication and then synchronization.​  
+Files under DROPS WAP pass through two stages: replication and then synchronization.​  
 
-* Data from production files is replicated into the new file formats in \[PRODUCT\] library.​  
+* Data from production files is replicated into the new file formats in DROPS WAP library.​  
 * New format data is kept in synchronization with production changes via IBM i Journals.​  
-* The synchronization is maintained until \[PRODUCT\] stops.​  
+* The synchronization is maintained until DROPS WAP stops.​  
 
-\[PRODUCT\] can be stopped and re-started, such as to perform a system backup. It maintains its last known replication or synchronization in its memory.​  
+DROPS WAP can be stopped and re-started, such as to perform a system backup. It maintains its last known replication or synchronization in its memory.​  
 
-\[PRODUCT\] is stopped by a macro-command after ending application activity. The macro-command invokes \[REDACTED\] to move the new files and other objects into target libraries.  
+DROPS WAP is stopped by a macro-command after ending application activity. The macro-command invokes ARCAD to move the new files and other objects into target libraries.  
 
-### \[PRODUCT\] in action
+### DROPS WAP in action
 
 ***Setup up the solution***  
 
-* Activate the use of \[PRODUCT\] with the \[REDACTED\] distribution process on the development site (*\[link\]* Setup on the Development site) and the production (target) site (*\[link\]* Setup on the Production site).
+* Activate the use of DROPS WAP with the ARCAD distribution process on the development site (*\[link\]* Setup on the Development site) and the production (target) site (*\[link\]* Setup on the Production site).
 
-* Configure the \[PRODUCT\] Web Studio to work with your \[REDACTED\] server (*\[link\]* Source connectors).
+* Configure the DROPS WAP Web Studio to work with your ARCAD server (*\[link\]* Source connectors).
 
 
 ***Analyze your files***
 
-* The first general consideration when using \[PRODUCT\] is to make sure you know what files to include in the process. Analyze your application and decide what files to include (*\[link\]* Analyze your application).
+* The first general consideration when using DROPS WAP is to make sure you know what files to include in the process. Analyze your application and decide what files to include (*\[link\]* Analyze your application).
 
 
-***Launch \[PRODUCT\] with \[REDACTED\] macro-commands***  
+***Launch DROPS WAP with ARCAD macro-commands***  
 
 * Run the DISTRIB macro-command to start the distribution of your application release (*\[link\]* Distributing with macros).
 
-* Edit and validate the list of files to be managed with \[PRODUCT\] (*\[link\]* Edit the list of files (LSTWAP)) when the macro-command displays this list.
+* Edit and validate the list of files to be managed with DROPS WAP (*\[link\]* Edit the list of files (LSTWAP)) when the macro-command displays this list.
 
-* Ensure the process of \[PRODUCT\] starts (*\[link\]* Monitoring DWBASE and DWSTRJRNE​ jobs launched to batch).
+* Ensure the process of DROPS WAP starts (*\[link\]* Monitoring DWBASE and DWSTRJRNE​ jobs launched to batch).
 
 
-***Monitor progress with the \[PRODUCT\] Web Studio***  
+***Monitor progress with the DROPS WAP Web Studio***  
 
-* Monitor the progress of the replication and the synchronization on the \[PRODUCT\] Web Studio (*\[link\]* Monitoring file replication).
+* Monitor the progress of the replication and the synchronization on the DROPS WAP Web Studio (*\[link\]* Monitoring file replication).
 
-* Wait until all files are copied and synchronized with journals before stopping the live application environment where the new release will be installed. \[PRODUCT\] keeps the file data synchronized until you stop it.
+* Wait until all files are copied and synchronized with journals before stopping the live application environment where the new release will be installed. DROPS WAP keeps the file data synchronized until you stop it.
 
 
 ***Transfer to production***  
 
-* The Transfer to production is the end of the process, when your data is ready to be deployed along with the rest of the release. When you want to end the production application and to move the new release into production, run the RCVNTWA2 macro-command ending the \[PRODUCT\] process.
+* The Transfer to production is the end of the process, when your data is ready to be deployed along with the rest of the release. When you want to end the production application and to move the new release into production, run the RCVNTWA2 macro-command ending the DROPS WAP process.