Push the button...

content/commands/ft.search/index.md

@@ -478,6 +478,8 @@ orders the results by the value of this attribute. This applies to both text and
 <summary><code>LIMIT first num</code></summary>
 
 limits the results to the offset and number of results given. Note that the offset is zero-indexed. The default is 0 10, which returns 10 items starting from the first result. You can use `LIMIT 0 0` to count the number of documents in the result set without actually returning them.
+
+**`LIMIT` behavior**:  If you use the `LIMIT` option without sorting, the results returned are non-deterministic, which means that subsequent queries may return duplicated or missing values. Add `SORTBY` with a unique field, or use `FT.AGGREGATE` with the `WITHCURSOR` option to ensure deterministic result set paging.
 </details>
 
 <details open>

content/develop/interact/search-and-query/query/vector-search.md

@@ -46,9 +46,9 @@ You can read more about the `PARAMS` argument in the [FT.SEARCH]({{< baseurl >}}
 
 The following example shows you how to query for three bikes based on their description embeddings, and by using the field alias `vector`. The result is returned in ascending order based on the distance. You can see that the query only returns the fields `__vector_score` and `description`. The field `__vector_score` is present by default. Because you can have multiple vector fields in your schema, the vector score field name depends on the name of the vector field. If you change the field name `@vector` to `@foo`, the score field name changes to `__foo_score`.
 
-```
+{{< clients-example query_vector vector1 >}}
 FT.SEARCH idx:bikes_vss "(*)=>[KNN 3 @vector $query_vector]" PARAMS 2 "query_vector" "Z\xf8\x15:\xf23\xa1\xbfZ\x1dI>\r\xca9..." SORTBY "__vector_score" ASC RETURN 2 "__vector_score" "description" DIALECT 2
-```
+{{< /clients-example >}}
 
 <!-- Python query>
 query = (
@@ -60,7 +60,7 @@ query = (
 </!-->
 
 {{% alert title="Note" color="warning" %}}
-The binary value of the query vector is significantly shortened in this example.
+The binary value of the query vector is significantly shortened in the CLI example above.
 {{% /alert  %}}
 
 
@@ -93,9 +93,9 @@ By default, [`FT.SEARCH`]({{< baseurl >}}/commands/ft.search/) returns only the
 
 The example below shows a radius query that returns the description and the distance within a radius of `0.5`. The result is sorted by the distance.
 
-```
+{{< clients-example query_vector vector2 >}}
 FT.SEARCH idx:bikes_vss "@vector:[VECTOR_RANGE 0.5 $query_vector]=>{$YIELD_DISTANCE_AS: vector_dist}" PARAMS 2 "query_vector" "Z\xf8\x15:\xf23\xa1\xbfZ\x1dI>\r\xca9..." SORTBY vector_dist ASC RETURN 2 vector_dist description DIALECT 2
-```
+{{< /clients-example >}}
 
 <!-- Python query>
 query = (

content/operate/kubernetes/deployment/openshift/openshift-operatorhub.md

@@ -29,7 +29,7 @@ To see which version of Redis Enterprise for Kubernetes supports your OpenShift
 
     Only one namespace per operator is supported.
 
-4. Update the **channel** with the version you're installing. 
+4. Update the **channel** with the version you're installing.
 
     For more information about specific versions, see the [release notes]({{< relref "/operate/kubernetes/release-notes/" >}}).
 
@@ -66,11 +66,15 @@ You only need to install the SCC once, but you must not delete it.
 After the install, the OperatorHub automatically uses the constraint for Redis Enterprise node pods.
 
 {{< note >}}
-**Known Limitation** - The automatic use of the security constraint is limited. The
-Redis Enterprise must be named `rec` for the constraint to be used automatically.  **Use the cluster name `rec` when deploying with the OperatorHub.**
+If you are using the recommended RedisEnterpriseCluster name of `rec`, the SCC is automatically bound to the RedisEnterpriseCluster after install.
+
+If you choose a different name for the RedisEnterpriseCluster, or override the default service account name, you must manually bind the SCC to the RedisEnterpriseCluster’s service account:
+
+  ```sh
+  oc adm policy add-scc-to-user redis-enterprise-scc-v2 \
+  system:serviceaccount:<my-project>:<rec-service-account-name>
+  ```
 
-If you require a different name, you must grant the SCC to the project
-namespace.
 {{< /note >}}
 
 ## Create Redis Enterprise custom resources

content/operate/rc/supported-regions.md

@@ -44,7 +44,7 @@ Redis Cloud Pro databases on AWS support [VPC Peering]({{< relref "/operate/rc/s
 | `eu-north-1` | Stockholm, Sweden | <span title="Supported">&#x2705;</span> | <span title="Not supported">&#x274c;</span> |
 | `eu-south-1` | Milan, Italy | <span title="Supported">&#x2705;</span> | <span title="Not supported">&#x274c;</span> |
 | `eu-south-2` | Spain | <span title="Supported">&#x2705;</span> | <span title="Not supported">&#x274c;</span> |
-| `eu-west-1` | Ireland | <span title="Supported">&#x2705;</span> | <span title="Not supported">&#x274c;</span> |
+| `eu-west-1` | Ireland | <span title="Supported">&#x2705;</span> | <span title="Supported">&#x2705;</span> |
 | `eu-west-2` | London, UK | <span title="Supported">&#x2705;</span> | <span title="Supported">&#x2705;</span> |
 | `eu-west-3` | Paris, France | <span title="Supported">&#x2705;</span> | <span title="Supported">&#x2705;</span> |
 

layouts/partials/tabs/wrapper.html

@@ -12,7 +12,8 @@
     {{ range $i, $tab := $tabs }}
         {{ $tid := printf "%s_%s" (replace (replace (index $tab "title") "#" "sharp") "." "") $id }}
         {{ $pid := printf "panel_%s" $tid }}
-        <input tabindex="1" type="radio" name="{{ $id }}" id="{{ $tid }}" data-lang="{{ index $tab "language" }}" class="radiotab w-0 h-0"
+        {{ $dataLang := replace (or (index $tab "language") "redis-cli") "C#" "dotnet" }}
+        <input tabindex="1" type="radio" name="{{ $id }}" id="{{ $tid }}" data-lang="{{ $dataLang }}" class="radiotab w-0 h-0"
                {{ if eq $i 0 }}checked{{ end }}
         />
         <label class="justify-left label ml-4 pt-3.5 px-3 pb-1 cursor-pointer text-sm text-center bg-redis-ink-900