docs(opensearch): record accessor syntax links (#1191)

Link to record accessor docs was wrong.
Syntax in FAQ example used double quotes instead of single quotes, which is not valid.

Signed-off-by: Lukas <[email protected]>

Author: Lukas

pipeline/outputs/opensearch.md

@@ -28,7 +28,7 @@ The following instructions assumes that you have a fully operational OpenSearch
 | Type | Type name. This option is ignored if `Suppress_Type_Name` is enabled.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | \_doc |
 | Logstash\_Format | Enable Logstash format compatibility. This option takes a boolean value: True/False, On/Off                                                                                                                                                                                                                                                                                                                                                                  | Off |
 | Logstash\_Prefix | When Logstash\_Format is enabled, the Index name is composed using a prefix and the date, e.g: If Logstash\_Prefix is equals to 'mydata' your index will become 'mydata-YYYY.MM.DD'. The last string appended belongs to the date when the data is being generated.                                                                                                                                                                                          | logstash |
-| Logstash\_Prefix\_Key | When included: the value of the key in the record will be evaluated as key reference and overrides Logstash\_Prefix for index generation. If the key/value is not found in the record then the Logstash\_Prefix option will act as a fallback. The parameter is expected to be a [record accessor](../../administration/configuring-fluent-bit/classic-mode/record-accessor). |  |
+| Logstash\_Prefix\_Key | When included: the value of the key in the record will be evaluated as key reference and overrides Logstash\_Prefix for index generation. If the key/value is not found in the record then the Logstash\_Prefix option will act as a fallback. The parameter is expected to be a [record accessor](../../administration/configuring-fluent-bit/classic-mode/record-accessor.md). |  |
 | Logstash\_Prefix\_Separator | Set a separator between logstash_prefix and date.                                                                                                           | - |
 | Logstash\_DateFormat | Time format \(based on [strftime](http://man7.org/linux/man-pages/man3/strftime.3.html)\) to generate the second part of the Index name.                                                                                                                                                                                                                                                                                                                     | %Y.%m.%d |
 | Time\_Key | When Logstash\_Format is enabled, each record will get a new timestamp field. The Time\_Key property defines the name of that field.                                                                                                                                                                                                                                                                                                                         | @timestamp |
@@ -139,7 +139,7 @@ The following snippet demonstrates using the namespace name as extracted by the
     Match *
     # ...
     Logstash_Prefix logstash
-    Logstash_Prefix_Key $kubernetes["namespace_name"]
+    Logstash_Prefix_Key $kubernetes['namespace_name']
     # ...
 ```
 
@@ -242,4 +242,4 @@ Alternatively, running this command to manually create a new index will return a
 PUT <index-name>
 ```
 
-There are multiple ways to resolve excessive shard usage in an OpenSearch domain such as deleting or combining indexes, adding more data nodes to the cluster, or updating the domain's index creation and sharding strategy. Consult the OpenSearch documentation for more information on how to use these strategies.
+There are multiple ways to resolve excessive shard usage in an OpenSearch domain such as deleting or combining indexes, adding more data nodes to the cluster, or updating the domain's index creation and sharding strategy. Consult the OpenSearch documentation for more information on how to use these strategies.