Fix more links: baseurl -> link; properly close {% with %}

docs/cloud/index.md

@@ -11,7 +11,7 @@ has_toc: false
 [lakeFS Cloud](https://lakefs.cloud) is a fully-managed lakeFS solution provided by Treeverse, implemented using our best practices, providing high availability, auto-scaling, support and enterprise-ready features.
 
 ## lakeFS Cloud Features
-* [Role-Based Access Control]({{ site.baseurl }}/reference/rbac.md)
+* [Role-Based Access Control]({% link reference/rbac.md %})
 * [Auditing](./auditing.md)
 * [Single-Sign-On](./sso.md) (including support for SAML, OIDC, AD FS, Okta, and Azure AD)
 * [Managed Garbage Collection](./managed-gc.md)

docs/howto/import.md

@@ -23,10 +23,10 @@ To avoid copying the data, lakeFS offers [Zero-copy import](#zero-copy-import).
 
 To run import you need the following permissions:
 `fs:WriteObject`, `fs:CreateMetaRange`, `fs:CreateCommit`, `fs:ImportFromStorage` and `fs:ImportCancel`. 
-The first 3 permissions are available by default to users in the default Developers group ([RBAC]({% link reference/rbac.md })) or the 
-Writers group ([ACL]({% link reference/access-control-lists.md })). The `Import*` permissions enable the user to import data from any location of the storage 
+The first 3 permissions are available by default to users in the default Developers group ([RBAC]({% link reference/rbac.md %})) or the 
+Writers group ([ACL]({% link reference/access-control-lists.md %})). The `Import*` permissions enable the user to import data from any location of the storage 
 provider that lakeFS has access to and cancel the operation if needed. 
-Thus, it's only available to users in group Supers ([ACL]({% link reference/access-control-lists.md})) or SuperUsers([RBAC]({% link reference/rbac.md})).
+Thus, it's only available to users in group Supers ([ACL]({% link reference/access-control-lists.md %})) or SuperUsers([RBAC]({% link reference/rbac.md %})).
 RBAC installations can modify policies to add that permission to any group, such as Developers.
 
 
@@ -115,7 +115,7 @@ To import using the UI, lakeFS must have permissions to list the objects in the
 
 1. In your repository's main page, click the _Import_ button to open the import dialog:
 
-   ![img.png]({% link assets/img/UI-Import-Dialog.png })
+   ![img.png]({% link assets/img/UI-Import-Dialog.png %})
 
 2. Under _Import from_, fill in the location on your object store you would like to import from.
 3. Fill in the import destination in lakeFS 
@@ -131,7 +131,7 @@ Once the import is complete, the changes are merged into the destination branch.
 
 ### _lakectl import_
 
-Prerequisite: have [lakectl]({% link reference/cli.md}) installed.
+Prerequisite: have [lakectl]({% link reference/cli.md %}) installed.
 
 The _lakectl import_ command acts the same as the UI import wizard. It commits the changes to a dedicated branch, with an optional
 flag to merge the changes to `<branch_name>`.
@@ -170,7 +170,7 @@ lakectl import \
 1. Importing is only possible from the object storage service in which your installation stores its data. For example, if lakeFS is configured to use S3, you cannot import data from Azure.
 2. Import is available for S3, GCP and Azure.
 3. For security reasons, if you are lakeFS on top of your local disk, you need to enable the import feature explicitly. 
-   To do so, set the `blockstore.local.import_enabled` to `true` and specify the allowed import paths in `blockstore.local.allowed_external_prefixes` (see [configuration reference]({% link reference/configuration.md})).
+   To do so, set the `blockstore.local.import_enabled` to `true` and specify the allowed import paths in `blockstore.local.allowed_external_prefixes` (see [configuration reference]({% link reference/configuration.md %})).
    Since there are some differences between object-stores and file-systems in the way directories/prefixes are treated, local import is allowed only for directories.
 
 ### Working with imported data