Fix links

Author: aversey

docs/setup_installation/admin/alert.md

@@ -40,7 +40,7 @@ button on the left side of the **email** row and fill out the form that pops up.
   CRAM-MD5, LOGIN or PLAIN.
 
 Optionally cluster wide Email alert receivers can be added in _Default receiver emails_.
-These receivers will be available to all users when they create event triggered [alerts](../../../user_guides/fs/feature_group/data_validation_best_practices#setup-alerts).
+These receivers will be available to all users when they create event triggered [alerts](../../user_guides/fs/feature_group/data_validation_best_practices.md#setup-alerts).
 
 ### Step 3: Configure Slack Alerts
 
@@ -56,7 +56,7 @@ Click on the _Configure_ button on the left side of the **slack** row and past i
 </figure>
 
 Optionally cluster wide Slack alert receivers can be added in _Slack channel/user_.
-These receivers will be available to all users when they create event triggered [alerts](../../../user_guides/fs/feature_group/data_validation_best_practices/#setup-alerts).
+These receivers will be available to all users when they create event triggered [alerts](../../user_guides/fs/feature_group/data_validation_best_practices.md#setup-alerts).
 
 ### Step 4: Configure Pagerduty Alerts
 
@@ -130,7 +130,7 @@ global:
  ...
 ```
 
-To test the alerts by creating triggers from Jobs and Feature group validations see [Alerts](../../../user_guides/fs/feature_group/data_validation_best_practices/#setup-alerts).
+To test the alerts by creating triggers from Jobs and Feature group validations see [Alerts](../../user_guides/fs/feature_group/data_validation_best_practices.md#setup-alerts).
 
 The yaml syntax in the UI is slightly different in that it does not allow double quotes (it will ignore the values but give no error).
 Below is an example configuration, that can be used in the UI, with both email and slack receivers configured for system alerts.

docs/setup_installation/admin/configure-project-mapping.md

@@ -1,14 +1,14 @@
 # Configure group to project mapping
- 
+
 ## Introduction
 A group-to-project mapping lets you automatically add all members of a Hopsworks group to a project, eliminating the need to add each user individually. To create a mapping, you simply select a Hopsworks group, choose the project it should be linked to, and assign the role that its members will have within that project.
 
 Once a mapping is created, project membership is controlled through Hopsworks group membership. Any updates made to the Hopsworks group—such as adding or removing users—will automatically be reflected in the project membership. For example, if a user is removed from the Hopsworks group, they will also be removed from the corresponding project.
- 
+
 ## Prerequisites
 
-1. Hopsworks group mapping sync enabled. This can be done by setting the variable ```hw_group_mapping_sync_enabled=true```. 
-See [Cluster Configuration](../variables.md) on how to change variable values in Hopsworks.
+1. Hopsworks group mapping sync enabled. This can be done by setting the variable ```hw_group_mapping_sync_enabled=true```.
+See [Cluster Configuration](./variables.md) on how to change variable values in Hopsworks.
 <figure>
  <a  href="../../../../assets/images/admin/project-mapping/configuration-variables.png">
    <img src="../../../../assets/images/admin/project-mapping/configuration-variables.png" alt="Enable Hopsworks mapping" />
@@ -24,56 +24,56 @@ If you can not find the variable ```hw_group_mapping_sync_enabled``` create it b
  </a>
  <figcaption>Create Hopsworks group mapping enabled variable</figcaption>
 </figure>
- 
+
 ### Step 1: Create a mapping
 To create a mapping go to **Cluster Settings** by clicking on your name in the top right
 corner of the navigation bar and choosing *Cluster Settings* from the dropdown menu.
 In the _Project mapping_ tab, you can create a new mapping by clicking on _Create new mapping_.
- 
+
 <figure>
  <a  href="../../../../assets/images/admin/project-mapping/project-mapping-empty.png">
    <img src="../../../../assets/images/admin/project-mapping/project-mapping-empty.png" alt="Project mapping tab" />
  </a>
  <figcaption>Project mapping</figcaption>
 </figure>
- 
+
 This will take you to the create mapping page shown below
 <figure>
  <a  href="../../../../assets/images/admin/project-mapping/create-hw-mapping.png">
    <img src="../../../../assets/images/admin/project-mapping/create-hw-mapping.png" alt="Create mapping" />
  </a>
  <figcaption>Create mapping</figcaption>
 </figure>
- 
+
 Here you can enter your Hopsworks group and map it to a project from the _Project_ drop down list.
 You can also choose the _Project role_ users will be assigned when they are added to the project.
- 
+
 Finally, click on _Create mapping_ and go back to mappings. You should see the newly created mapping(s) as shown below.
- 
+
 <figure>
  <a  href="../../../../assets/images/admin/project-mapping/group-to-project-mappings.png">
    <img src="../../../../assets/images/admin/project-mapping/group-to-project-mappings.png" alt="Project mappings" />
  </a>
  <figcaption>Project mappings</figcaption>
 </figure>
-  
+
 ### Step 2: Edit a mapping
- 
+
 From the list of mappings click on the edit button (:material-pencil:). This will open a popup that will allow you to change the _group_, _project name_, and _project role_ of a mapping.
- 
+
 <figure>
  <a  href="../../../../assets/images/admin/project-mapping/edit-hw-mapping.png">
    <img src="../../../../assets/images/admin/project-mapping/edit-hw-mapping.png" alt="Edit mapping" />
  </a>
  <figcaption>Edit mapping</figcaption>
 </figure>
- 
+
 !!!Warning
     Updating a mapping's _group_ or _project name_ will remove all members of the previous group from the project.
- 
+
 ### Step 3: Delete a mapping
- 
+
 To delete a mapping click on the delete button.
- 
+
 !!!Warning
     Deleting a mapping will remove all members of that group from the project.

docs/setup_installation/admin/ldap/configure-project-mapping.md

@@ -66,7 +66,9 @@ Finally, click on *Create mapping* and go back to mappings. You should see the n
 !!!Note
     If there are no groups in the *Remote group* drop down list check if **ldap_groups_search_filter** is correct by using the value in ```ldapsearch``` replacing ```%c``` with ```*```, as shown in the example below.
 
-    ```ldapsearch -LLL -H ldap:/// -b '<base dn>' -D '<user dn>' -w <password> '(&(objectClass=groupOfNames)(cn=*))'```
+    ```bash
+    ldapsearch -LLL -H ldap:/// -b '<base dn>' -D '<user dn>' -w <password> '(&(objectClass=groupOfNames)(cn=*))'
+    ```
 
     This should return all the groups in your LDAP.
     See [Cluster Configuration](../variables.md) on how to find and update the value of this variable.

docs/user_guides/client_installation/index.md

@@ -48,11 +48,11 @@ pip install hopsworks[python,great-expectations,polars]
 
 If you want to interact with the Hopsworks Feature Store from environments such as Spark, Flink or Beam, you can use the Hopsworks Feature Store (HSFS) Java library.
 
-!!!note "Feature Store Only"
+!!! note "Feature Store Only"
 
     The Java library only allows interaction with the Feature Store component of the Hopsworks platform.
     Additionally each environment might restrict the supported API operation.
-    You can see which API operation is supported by which environment [here](./fs/compute_engines.md)
+    You can see which API operation is supported by which environment [here](../fs/compute_engines.md)
 
 The HSFS library is available on the Hopsworks' Maven repository.
 If you are using Maven as build tool, you can add the following in your `pom.xml` file:

docs/user_guides/fs/feature_group/on_demand_transformations.md

@@ -60,7 +60,7 @@ The features to be used by the on-demand transformation function can be specifie
 
 ## Usage
 
-On-demand transformation functions attached to a feature group are automatically executed in the feature pipeline when you [insert data](../create/#batch-write-api) into a feature group and [by the Python client while retrieving feature vectors](../feature_view/feature-vectors.md#retrieval) for online inference using feature views that contain on-demand features.
+On-demand transformation functions attached to a feature group are automatically executed in the feature pipeline when you [insert data](./create.md#batch-write-api) into a feature group and [by the Python client while retrieving feature vectors](../feature_view/feature-vectors.md#retrieval) for online inference using feature views that contain on-demand features.
 
 The on-demand features computed by on-demand transformation functions are positioned after all other features in a feature group and are ordered alphabetically by their names.
 

docs/user_guides/fs/feature_monitoring/index.md

@@ -38,7 +38,7 @@ Moreover, windows can stick to a _specific point in time_ (e.g., static window)
 These types of windows apply to both _detection_ and _reference_ windows.
 Different types of windows allows for different use cases depending on whether you enable feature monitoring on your Feature Groups or Feature Views.
 
-See more details about _detection_ and _reference_ windows in the [Detection windows](scheduled_statistics.md#detection-windows) and [Reference windows](statistics_comparison#reference-windows) guides.
+See more details about _detection_ and _reference_ windows in the [Detection windows](./scheduled_statistics.md#detection-windows) and [Reference windows](./statistics_comparison.md#reference-windows) guides.
 
 ## Visualize statistics on a time series
 

docs/user_guides/integrations/index.md

@@ -3,12 +3,12 @@
 Hopsworks is an open platform aiming to be accessible from a variety of tools.
 Learn in this section how to connect to Hopsworks from
 
-- [Python, AWS SageMaker, Google Colab, Kubeflow](python)
-- [Java](java)
-- [Databricks](databricks/networking)
-- [AWS EMR](emr/emr_configuration)
-- [Azure HDInsight](hdinsight)
-- [Azure Machine Learning](mlstudio_designer)
-- [Apache Spark](spark)
-- [Apache Flink](flink)
-- [Apache Beam](beam)
+- [Python, AWS SageMaker, Google Colab, Kubeflow](./python.md)
+- [Java](./java.md)
+- [Databricks](./databricks/networking.md)
+- [AWS EMR](./emr/emr_configuration.md)
+- [Azure HDInsight](./hdinsight.md)
+- [Azure Machine Learning](./mlstudio_designer.md)
+- [Apache Spark](./spark.md)
+- [Apache Flink](./flink.md)
+- [Apache Beam](./beam.md)

docs/user_guides/mlops/serving/deployment.md

@@ -219,7 +219,7 @@ Artifact versions are unique for the same model version.
 
 When a new deployment is created, a new artifact version is generated in two cases:
 
-- the artifact version in the predictor is set to `CREATE` (see [Artifact Version](../predictor/#artifact_version))
+- the artifact version in the predictor is set to `CREATE` (see [Artifact Version](./predictor.md#artifact_version))
 - no model artifact with the same files has been created before.
 
 Inside a model deployment, the local path to the artifact files is stored in the `ARTIFACT_FILES_PATH` environment variable (see [environment variables](../serving/predictor.md#environment-variables)).

docs/user_guides/projects/iam_role/iam_role_chaining.md

@@ -12,7 +12,7 @@ Before you begin this guide you'll need the following:
 - A Hopsworks cluster running on EC2.
 - [Role chaining](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_terms-and-concepts.html#iam-term-role-chaining) setup in AWS.
 - Configure role mappings in Hopsworks.
-  For a guide on how to configure this see [AWS IAM Role Chaining](../../setup_installation/admin/roleChaining.md).
+  For a guide on how to configure this see [AWS IAM Role Chaining](../../../setup_installation/admin/roleChaining.md).
 
 ## UI
 

docs/user_guides/projects/opensearch/connect.md

@@ -39,4 +39,4 @@ client = OpenSearch(**opensearch_api.get_default_py_config())
 
 ## Going Further
 
-You can now use the client to interact directly with the OpenSearch cluster, such as [vector database](../../mlops/vector_database/index.md).
+You can now use the client to interact directly with the OpenSearch cluster, such as [vector database](../../../concepts/mlops/opensearch.md).