windturbine_anomaly_detection: Fixed the docs link (open-edge-platform#272)

Signed-off-by: Pooja Kumbharkar <pooja.kumbharkar@intel.com>

Author: pooja-intel

manufacturing-ai-suite/wind-turbine-anomaly-detection/README.md

@@ -6,7 +6,7 @@ Wind Turbine Anomaly Detection sample application demonstrates a time series use
 
 - **Overview**
   - [Overview](docs/user-guide/Overview.md): A high-level introduction.
-  - [Architecture](docs/user-guide/Overview.md#high-level-architecture): High Level Architecture.
+  - [Architecture](docs/user-guide/how-it-works.md#high-level-architecture): High Level Architecture.
 
 - **Getting Started**
   - [System Requirements](docs/user-guide/system-requirements.md): Hardware and software requirements for running the sample application.

manufacturing-ai-suite/wind-turbine-anomaly-detection/docs/user-guide/how-to-build-from-source.md

@@ -2,7 +2,7 @@
 
 This guide provides step-by-step instructions for building the `Time Series Analytics`
 microservice and `Wind Turbine Anomaly Detection` Sample Application from source.
-Please follow [prerequisites](./get-started.md#prerequisites) and understand [data flow explanation](./get-started.md#data-flow-explanation)
+Please follow [prerequisites](./get-started.md#configure-docker) and understand [data flow explanation](./get-started.md#data-flow-explanation)
 before proceeding with the below steps.
 
 ## Steps to Build from Source

manufacturing-ai-suite/wind-turbine-anomaly-detection/docs/user-guide/how-to-configure-alerts.md

@@ -144,7 +144,7 @@ curl -X 'POST' \
 
 - **Publish MQTT Alerts**
 
-For detailed instructions on configuring and publishing MQTT alerts, refer to the [Publishing MQTT Alerts](#publishing-mqtt-alerts) section.
+For detailed instructions on configuring and publishing MQTT alerts, refer to the [Publish MQTT Alerts](#publish-mqtt-alerts) section.
 
 - **Subscribe to MQTT Alerts**
 
@@ -181,7 +181,7 @@ To enable OPC-UA alerts in `Time Series Analytics Microservice`, please follow b
 
 1. Configuring OPC-UA Alert in TICK Script
 
-Configure the tick script by following [these instructions](#1-configuring-opc-ua-alert-in-tick-script).
+Configure the tick script by following [these instructions](#1-configure-opc-ua-alert-in-tick-script).
 
 2. Copying the TICK script
 
@@ -190,8 +190,8 @@ Copy the TICK script using the following command:
 ```sh
 cd edge-ai-suites/manufacturing-ai-suite/wind-turbine-anomaly-detection # path relative to git clone folder
 cd time_series_analytics_microservice
-mkdir windturbine_anomaly_detector
-cp -r tick_scripts windturbine_anomaly_detector/.
+mkdir -p windturbine_anomaly_detector
+cp -r models tick_scripts udfs windturbine_anomaly_detector/.
 
 POD_NAME=$(kubectl get pods -n ts-wind-turbine-anomaly-app -o jsonpath='{.items[*].metadata.name}' | tr ' ' '\n' | grep deployment-time-series-analytics-microservice | head -n 1)
 
@@ -228,7 +228,7 @@ curl -X 'POST' \
 
 - **Subscribe to OPC UA Alerts using Sample OPCUA Subscriber**
 
-To subscribe to OPC-UA alerts, follow [these steps](#subscribing-to-opc-ua-alerts-using-sample-opcua-subscriber).
+To subscribe to OPC-UA alerts, follow [these steps](#subscribe-to-opc-ua-alerts-using-sample-opcua-subscriber).
 
 ## Supporting Resources
 

manufacturing-ai-suite/wind-turbine-anomaly-detection/docs/user-guide/how-to-configure-custom-udf.md

@@ -44,7 +44,7 @@ This guide provides instructions for setting up custom UDF deployment package (U
        - Key sections:
          - **Input**: Fetch data from Telegraf (stream).
          - **Processing**: Apply UDFs for analytics.
-         - **Alerts**: Configuration for publishing alerts (e.g., MQTT). Refer [link](#Publishing-mqtt-alerts)
+         - **Alerts**: Configuration for publishing alerts (e.g., MQTT). Refer [link](./how-to-configure-alerts.md#publish-mqtt-alerts)
          - **Logging**: Set log levels (`INFO`, `DEBUG`, `WARN`, `ERROR`).
          - **Output**: Publish processed data.
 
@@ -69,7 +69,7 @@ and config.json has been volume mounted for the Time Series Analytics Microservi
 
 1. Update the UDF deployment package by following the instructions in [Configure Time Series Analytics Microservice with Custom UDF Deployment Package](./how-to-configure-custom-udf.md#configure-time-series-analytics-microservice-with-custom-udf-deployment-package).
 
-2. Copy the updated UDF deployment package using the [steps above](#copy-the-windturbine_anomaly_detection-udf-package-for-helm-deployment-to-time-series-analytics-microservice).
+2. Copy the updated UDF deployment package using the [steps](./how-to-deploy-with-helm.md#copy-the-windturbine_anomaly_detection-udf-package-for-helm-deployment-to-time-series-analytics-microservice).
 
 3. Make the following REST API call to the Time Series Analytics microservice for the updated custom UDF:
     ```sh

manufacturing-ai-suite/wind-turbine-anomaly-detection/docs/user-guide/how-to-enable-system-metrics.md

@@ -2,7 +2,7 @@
 
 > **Note**: The system metrics dashboard is only supported with docker compose deployments and requires `Telegraf` to run as the `root` user.
 
-Please follow [prerequisites](./get-started.md#prerequisites) and understand [data flow explanation](./get-started.md#data-flow-explanation) as
+Please follow [prerequisites](./get-started.md#configure-docker) and understand [data flow explanation](./get-started.md#data-flow-explanation) as
 a prerequisite.
 
 To enable the system metrics dashboard showcasing the host and docker containers CPU, memory, network, disk IO usage, run the following command:

manufacturing-ai-suite/wind-turbine-anomaly-detection/helm/values.yaml

@@ -31,10 +31,10 @@ env:
   # MR_PSQL_PASSWORD length must be a minimum of 10 alphanumeric characters with atleast one digit
   POSTGRES_PASSWORD:
 
-  # MR_MINIO_ACCESS_KEY length must be a minimum of 10 alphanumeric characters with atleast one digit
-  MR_MINIO_ACCESS_KEY:
+  # MINIO_ACCESS_KEY length must be a minimum of 10 alphanumeric characters with atleast one digit
+  MINIO_ACCESS_KEY:
 
-  # MR_MINIO_SECRET_KEY length must be a minimum of 10 alphanumeric characters with atleast one digit
+  # MINIO_SECRET_KEY length must be a minimum of 10 alphanumeric characters with atleast one digit
   MINIO_SECRET_KEY:
 
   HTTP_PROXY: