[fixup] more {%...%} fixes

Close `{%` with `%}` not `}`.

docs/howto/deploy/aws.md

@@ -66,7 +66,7 @@ By default, lakeFS will create the required DynamoDB table if it does not alread
 
 DEBUG: I am {{ page.path }} !
 
-💡 You can also use lakeFS with PostgreSQL instead of DynamoDB! See the [configuration reference](% link /reference/configuration.md}) for more information.
+💡 You can also use lakeFS with PostgreSQL instead of DynamoDB! See the [configuration reference]({% link /reference/configuration.md%}) for more information.
 {: .note }
 
 ## Run the lakeFS server
@@ -95,7 +95,7 @@ Connect to your EC2 instance using SSH:
    blockstore:
      type: s3
    ```
-1. [Download the binary](% link /index.md}#downloads) to the EC2 instance.
+1. [Download the binary]({% link /index.md#downloads%}) to the EC2 instance.
 1. Run the `lakefs` binary on the EC2 instance:
 
    ```sh
@@ -133,7 +133,7 @@ To install lakeFS with Helm:
    ```
 1. Fill in the missing values and save the file as `conf-values.yaml`. For more configuration options, see our Helm chart [README](https://github.com/treeverse/charts/blob/master/charts/lakefs/README.md#custom-configuration){:target="_blank"}.
 
-   The `lakefsConfig` parameter is the lakeFS configuration documented [here](% link /reference/configuration.md}) but without sensitive information.
+   The `lakefsConfig` parameter is the lakeFS configuration documented [here]({% link /reference/configuration.md%}) but without sensitive information.
    Sensitive information like `databaseConnectionString` is given through separate parameters, and the chart will inject it into Kubernetes secrets.
    {: .note }
 
@@ -279,4 +279,4 @@ lakeFS can authenticate with your AWS account using an AWS user, using an access
  }
 ```
 
-% include_relative includes/setup.md %}
+{% include_relative includes/setup.md %}

docs/understand/faq.md

@@ -13,13 +13,13 @@ redirect_from:
 lakeFS is completely free, open-source, and licensed under the [Apache 2.0](https://www.apache.org/licenses/LICENSE-2.0) License. We maintain a public [product roadmap]({{ site.baseurl }}/project/index.html#roadmap) and a [Slack channel](https://lakefs.io/slack) for open discussions.
 
 ### 2. How does lakeFS data versioning work?
-lakeFS uses a copy-on-write mechanism to avoid data duplication. For example, creating a new branch is a metadata-only operation: no objects are actually copied. Only when an object changes does lakeFS create another [version of the data](https://lakefs.io/data-versioning/) in the storage. For more information, see [Versioning internals]({% link /understand/how/versioning-internals.md}).
+lakeFS uses a copy-on-write mechanism to avoid data duplication. For example, creating a new branch is a metadata-only operation: no objects are actually copied. Only when an object changes does lakeFS create another [version of the data](https://lakefs.io/data-versioning/) in the storage. For more information, see [Versioning internals]({% link /understand/how/versioning-internals.md%}).
 
 ### 3. How do I get support for my lakeFS installation?
 We are extremely responsive on our Slack channel, and we make sure to prioritize the most pressing issues for the community. For SLA-based support, please contact us at [[email protected]](mailto:[email protected]).
 
 ### 4. Do you collect data from your active installations?
-We collect anonymous usage statistics to understand the patterns of use and to detect product gaps we may have so we can fix them. This is optional and may be turned off by setting `stats.enabled` to `false`. See the [configuration reference]({% link /reference/configuration.md}#reference) for more details.
+We collect anonymous usage statistics to understand the patterns of use and to detect product gaps we may have so we can fix them. This is optional and may be turned off by setting `stats.enabled` to `false`. See the [configuration reference]({% link /reference/configuration.md#reference%}) for more details.
 
 
 The data we gather is limited to the following: