More fixes

Author: aversey

.markdownlint.yaml

@@ -1,5 +1,7 @@
 MD041: false
 MD013: false
 MD033: false
+MD045: false
+MD046: false
 MD004:
   style: dash

docs/concepts/fs/feature_view/offline_api.md

@@ -31,7 +31,7 @@ HSFS hides this complexity by performing the point-in-time JOIN transparently, s
 HSFS uses the event_time columns on both feature groups to determine the most recent (but not newer) feature values that are joined together with the feature values from the feature group containing the label.
 That is, the features in the feature group containing the label are the observation times for the features in the resulting training data, and we want feature values from the other feature groups that have the most recent timestamps, but not newer than the timestamp in the label-containing feature group.
 
-#### Spine Dataframes
+#### Spine Groups
 
 The left side of the point-in-time join is typically the set of training entities/primary key values for which the relevant features need to be retrieved.
 This left side of the join can also be replaced by a [spine group](../feature_group/spine_group.md).

docs/setup_installation/admin/alert.md

@@ -118,7 +118,7 @@ It will try to load the new configuration to the alertmanager and show any error
     If you make any changes to the configuration ensure that the changes are valid by reloading the configuration until the changes are loaded and visible in the advanced page.
 
 _Example:_ Adding the yaml snippet shown below in the global section of the alert manager configuration will
-have the same effect as creating the SMTP configuration as shown in [section 1](#1-email-alerts) above.
+have the same effect as creating the SMTP configuration as shown in [section 1](#step-2-configure-email-alerts) above.
 
 ```yaml
 global:

docs/setup_installation/admin/audit/export-audit-logs.md

@@ -18,20 +18,20 @@ Create a dataset and a table in [BigQuery](https://cloud.google.com/bigquery/doc
 
 The table schema is shown below.
 
-```
-fullname       mode     type     description
-pathInfo       NULLABLE STRING
-methodName       NULLABLE STRING
-caller           NULLABLE RECORD
-dateTime       NULLABLE TIMESTAMP bq-datetime
+```plaintext
+fullname        mode     type      description
+pathInfo        NULLABLE STRING
+methodName      NULLABLE STRING
+caller          NULLABLE RECORD
+dateTime        NULLABLE TIMESTAMP bq-datetime
 userAgent       NULLABLE STRING
-clientIp       NULLABLE STRING
-outcome           NULLABLE STRING
-parameters       NULLABLE STRING
+clientIp        NULLABLE STRING
+outcome         NULLABLE STRING
+parameters      NULLABLE STRING
 className       NULLABLE STRING
 caller.userId   NULLABLE STRING
-caller.email   NULLABLE STRING
-caller.username   NULLABLE STRING
+caller.email    NULLABLE STRING
+caller.username NULLABLE STRING
 ```
 
 ## Step 2: Export Audit Logs to the BigQuery Table

docs/setup_installation/admin/ha-dr/dr.md

@@ -54,7 +54,8 @@ The backup will be located locally on each datanode under the following path:
 /srv/hops/mysql-cluster/ndb/backups/BACKUP - the directory name will be BACKUP-[backup_id]
 ```
 
-A more comprehensive backup script is available [here](https://github.com/logicalclocks/ndb-chef/blob/master/templates/default/native_ndb_backup.sh.erb) - The script includes the steps above as well as collecting all the partial RonDB backups on a single node.
+You can check out [a more comprehensive backup script](https://github.com/logicalclocks/ndb-chef/blob/master/templates/default/native_ndb_backup.sh.erb).
+The script includes the steps above as well as collecting all the partial RonDB backups on a single node.
 The script is a good starting point and can be adapted to ship the database backup outside the cluster.
 
 ### HopsFS Backup

docs/setup_installation/admin/monitoring/export-metrics.md

@@ -67,14 +67,14 @@ kubectl -n $NAMESPACE get svc prometheus-external -ojsonpath='{.status.loadBalan
 !!!Warning
     It will take a few seconds until an IP address is assigned to the Service.
 
-We will use this IP address in Step 2.
+We will use this IP address in Step 3.
 
-#### Step 2
+#### Step 3
 
 Edit the configuration file of **Prometheus B** server and append the following Job under `scrape_configs`:
 
 !!! note
-    Replace IP_ADDRESS with the IP address from Step 1 or the IP address of Prometheus service if it is directly accessible.
+    Replace IP_ADDRESS with the IP address from Step 2 or the IP address of Prometheus service if it is directly accessible.
     The snippet below assumes Hopsworks services runs at Namespace **hopsworks**.
 
 ```yaml

docs/setup_installation/admin/oauth2/create-client.md

@@ -3,7 +3,7 @@
 ## Introduction
 
 Before registering your identity provider in Hopsworks you need to create a client application in your identity provider and acquire a _client id_ and a _client secret_.
-An example on how to create a client using [Okta](https://www.okta.com/) and [Azure Active Directory](https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/Overview) identity providers can be found [here](../create-okta-client) and [here](../create-azure-client) respectively.
+An example on how to create a client using [Okta](https://www.okta.com/) and [Azure Active Directory](https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/Overview) identity providers can be found in the following guides: [Create Okta Client](../create-okta-client) and [Create Azure Client](../create-azure-client).
 
 ## Prerequisites
 

docs/setup_installation/admin/project.md

@@ -48,7 +48,7 @@ As an example, a 100MB file stored with a replication factor of 3, will consume
 By default, all storage quotas are disabled and not enforced.
 Administrators can change this default by changing the following configuration in the [Configuration](../admin/variables.md) UI and/or the cluster definition:
 
-```
+```yaml
 hopsworks:
     featurestore_default_quota: [default quota in bytes, -1 to disable]
     hdfs_default_quota: [default quota in bytes, -1 to disable]
@@ -68,7 +68,7 @@ Currently, Hopsworks does not support defining quotas for compute scheduled on t
 By default, the compute quota is disabled.
 Administrators can change this default by changing the following configuration in the [Configuration](../admin/variables.md) UI and/or the cluster definition:
 
-```
+```yaml
 hopsworks:
     yarn_default_payment_type: [NOLIMIT to disable the quota, PREPAID to enable it]
     yarn_default_quota: [default quota in seconds]
@@ -95,7 +95,7 @@ By default, each user can create up to 10 projects.
 For production environments, the number of projects should be limited and controlled for resource allocation purposes as well as closer control over the data.
 Administrators can control how many projects a user can provision by setting the following configuration in the [Configuration](../admin/variables.md) UI and/or cluster definition:
 
-```
+```yaml
 hopsworks:
     max_num_proj_per_user: [Maximum number of projects each user can create]
 ```

docs/setup_installation/admin/roleChaining.md

@@ -136,6 +136,6 @@ And click on _Create new role chaining_
 </figure>
 
 Project member can now create connectors using _temporary credentials_ to assume the role you configured.
-More detail about using temporary credentials can be found [here](../../user_guides/fs/data_source/creation/s3.md#temporary-credentials).
+More details about using temporary credentials can be found in the [Temporary Credentials section](../../user_guides/fs/data_source/creation/s3.md#temporary-credentials) of the S3 datasource creation guide.
 
 Project member can see the list of role they can assume by going the _Project Settings_ -> [Assuming IAM Roles](../../../user_guides/projects/iam_role/iam_role_chaining) page.

docs/setup_installation/aws/getting_started.md

@@ -219,8 +219,7 @@ This section describes the steps required to deploy the Hopsworks stack using He
 
 - Configure Repo
 
-To obtain access to the Hopsworks helm chart repository, please obtain
-an evaluation/startup licence [here](https://www.hopsworks.ai/try).
+To obtain access to the Hopsworks helm chart repository, please [obtain](https://www.hopsworks.ai/try) an evaluation/startup licence.
 
 Once you have the helm chart repository URL, replace the environment
 variable $HOPSWORKS_REPO in the following command with this URL.