Fix links and liquid formatting error (#5512)

Signed-off-by: Fanit Kolchina <[email protected]>

_data-prepper/managing-data-prepper/configuring-data-prepper.md

@@ -151,11 +151,11 @@ sts_role_arn | No | String   | The AWS Security Token Service (AWS STS) role to
 refresh_interval | No | Duration | The refreshment interval for AWS secrets extension plugin to poll new secret values. Defaults to `PT1H`. See [Automatically refreshing secrets](#automatically-refreshing-secrets) for details.                             
 
 #### Reference secrets
-
+ß
 In `pipelines.yaml`, secret values can be referenced within the pipeline plugins using the following formats:
 
-* plaintext: `${{aws_secrets:<YOUR_SECRET_CONFIG_ID>}}`.
-* JSON (key-value pairs): `${{aws_secrets:<YOUR_SECRET_CONFIG_ID>:<YOUR_KEY>}}`
+* plaintext: `{% raw %}${{aws_secrets:<YOUR_SECRET_CONFIG_ID>}}{% endraw %}`.
+* JSON (key-value pairs): `{% raw %}${{aws_secrets:<YOUR_SECRET_CONFIG_ID>:<YOUR_KEY>}}{% endraw %}`
 
 
 Replace `<YOUR_SECRET_CONFIG_ID>` with the corresponding secret config ID under `/extensions/aws/secrets`. Replace `<YOUR_KEY>` with the desired key in the secret JSON value. The secret value reference string format can be interpreted for the following plugin setting data types:
@@ -194,9 +194,9 @@ After `<YOUR_SECRET_CONFIG_ID>` is configured, you can reference the IDs in your
 ```
 sink:
     - opensearch:
-        hosts: [ "${{aws_secrets:host-secret-config}}" ]
-        username: "${{aws_secrets:credential-secret-config:username}}"
-        password: "${{aws_secrets:credential-secret-config:password}}"
+        hosts: [ {% raw %}"${{aws_secrets:host-secret-config}}"{% endraw %} ]
+        username: {% raw %}"${{aws_secrets:credential-secret-config:username}}"{% endraw %}
+        password: {% raw %}"${{aws_secrets:credential-secret-config:password}}"{% endraw %}
         index: "test-migration"
 ```
 

_data-prepper/pipelines/pipelines.md

@@ -343,9 +343,9 @@ simple-sample-pipeline:
   ...
   sink:
     - opensearch:
-        hosts: [ "${{aws_secrets:host-secret-config}}" ]
-        username: "${{aws_secrets:credential-secret-config:username}}"
-        password: "${{aws_secrets:credential-secret-config:password}}"
+        hosts: [ {% raw %}"${{aws_secrets:host-secret-config}}"{% endraw %} ]
+        username: {% raw %}"${{aws_secrets:credential-secret-config:username}}"{% endraw %}
+        password: {% raw %}"${{aws_secrets:credential-secret-config:password}}"{% endraw %}
         index: "test-migration"
 ```
 

_query-dsl/full-text/match.md

@@ -8,7 +8,7 @@ nav_order: 10
 
 # Match query
 
-Use the `match` query for full-text search on a specific document field. If you run a `match` query on a [`text`]({{site.url}}/{{site.baseurl}}/field-types/supported-field-types/text/) field, the `match` query [analyzes]({{site.url}}/{{site.baseurl}}/analyzers/index/) the provided search string and returns documents that match any of the string's terms. If you run a `match` query on an exact-value field, it returns documents that match the exact value. The preferred way to search exact-value fields is to use a filter because, unlike a query, a filter is cached.
+Use the `match` query for full-text search on a specific document field. If you run a `match` query on a [`text`]({{site.url}}{{site.baseurl}}/field-types/supported-field-types/text/) field, the `match` query [analyzes]({{site.url}}{{site.baseurl}}/analyzers/index/) the provided search string and returns documents that match any of the string's terms. If you run a `match` query on an exact-value field, it returns documents that match the exact value. The preferred way to search exact-value fields is to use a filter because, unlike a query, a filter is cached.
 
 The following example shows a basic `match` query for the word `wind` in the `title`: