Sundry link fixes (#304)

* Sundry link fixes

* apply review comments

Author: dwdougherty

content/develop/data-types/hashes.md

@@ -88,8 +88,6 @@ The following commands can be used to add, delete, and report on a key's individ
 * [`HEXPIRETIME`]({{< relref "/commands/hexpiretime " >}}): get the expiration time as a Unix timestamp in seconds since the Unix epoch.
 * [`HPEXPIRETIME`]({{< relref "/commands/hpexpiretime " >}}): get the expiration time as a Unix timestamp in milliseconds since the Unix epoch.
 * [`HPERSIST`]({{< relref "/commands/hpersist " >}}): remove the expiration time from a key's fields.
-* [`HGETF`]({{< relref "/commands/hgetf " >}}): get a key field's value and optionally set the remaining time to live or UNIX expiration timestamp in seconds or milliseconds.
-* [`HSETF`]({{< relref "/commands/hsetf " >}}): set a key's fields to the specified values and optionally set the field's remaining time to live or UNIX expiration timestamp in seconds or milliseconds.
 * [`HTTL`]({{< relref "/commands/httl " >}}): get the remaining time to live in seconds for a key's fields.
 * [`HPTTL`]({{< relref "/commands/hpttl " >}}): get the remaining time to live in milliseconds for a key's fields.
 

content/develop/use/keyspace-notifications.md

@@ -104,7 +104,7 @@ Different commands generate different kind of events according to the following
 * [`HEXPIRE`]({{< relref "/commands/hexpire" >}}) and all its variants ([`HEXPIREAT`]({{< relref "/commands/hpexpireat" >}}), [`HPEXPIRE`]({{< relref "/commands/hpexpire" >}}), [`HPEXPIREAT`]({{< relref "/commands/hpexpireat" >}})) generate `hexpire` events.
 * [`HINCRBYFLOAT`]({{< relref "/commands/hincrbyfloat" >}}) generates an `hincrbyfloat` event.
 * [`HINCRBY`]({{< relref "/commands/hincrby" >}}) generates an `hincrby` event.
-* [`HPERSIST`]({{ < relref "/commands/hpersist" >}}) generates a `hpersist` event.
+* [`HPERSIST`]({{< relref "/commands/hpersist" >}}) generates an `hpersist` event.
 * [`HSET`]({{< relref "/commands/hset" >}}), [`HSETNX`]({{< relref "/commands/hsetnx" >}}) and [`HMSET`]({{< relref "/commands/hmset" >}}) all generate a single `hset` event.
 * [`INCRBYFLOAT`]({{< relref "/commands/incrbyfloat" >}}) generates an `incrbyfloat` events.
 * [`INCR`]({{< relref "/commands/incr" >}}), [`DECR`]({{< relref "/commands/decr" >}}), [`INCRBY`]({{< relref "/commands/incrby" >}}), [`DECRBY`]({{< relref "/commands/decrby" >}}) commands all generate `incrby` events.
@@ -143,9 +143,9 @@ Different commands generate different kind of events according to the following
 * [`XTRIM`]({{< relref "/commands/xtrim" >}}) generates an `xtrim` event.
 * [`ZADD`]({{< relref "/commands/zadd" >}}) generates a single `zadd` event even when multiple elements are added.
 * [`ZDIFFSTORE`]({{< relref "/commands/zdiffstore" >}}), [`ZINTERSTORE`]({{< relref "/commands/zinterstore" >}}) and [`ZUNIONSTORE`]({{< relref "/commands/zunionstore" >}}) respectively generate `zdiffstore`, `zinterstore` and `zunionstore` events. In the special case the resulting sorted set is empty, and the key where the result is stored already exists, a `del` event is generated since the key is removed.
-* [`ZINCR`]({{< relref "/commands/zincr" >}}) generates a `zincr` event.
-* [`ZREMBYRANK`]({{< relref "/commands/zrembyrank" >}}) generates a single `zrembyrank` event. When the resulting sorted set is empty and the key is generated, an additional `del` event is generated.
-* [`ZREMBYSCORE`]({{< relref "/commands/zrembyscore" >}}) generates a single `zrembyscore` event. When the resulting sorted set is empty and the key is generated, an additional `del` event is generated.
+* [`ZINCRBY`]({{< relref "/commands/zincrby" >}}) generates a `zincr` event.
+* [`ZREMRANGEBYRANK`]({{< relref "/commands/zremrangebyrank" >}}) generates a single `zrembyrank` event. When the resulting sorted set is empty and the key is generated, an additional `del` event is generated.
+* [`ZREMRANGEBYSCORE`]({{< relref "/commands/zremrangebyscore" >}}) generates a single `zrembyscore` event. When the resulting sorted set is empty and the key is generated, an additional `del` event is generated.
 * [`ZREM`]({{< relref "/commands/zrem" >}}) generates a single `zrem` event even when multiple elements are deleted. When the resulting sorted set is empty and the key is generated, an additional `del` event is generated.
 * Every time a key with a time to live associated is removed from the data set because it expired, an `expired` event is generated.
 * Every time a key is evicted from the data set in order to free memory as a result of the `maxmemory` policy, an `evicted` event is generated.

content/operate/rc/changelog/august-2023.md

@@ -22,7 +22,7 @@ You can opt in to Redis 7.2 on [Flexible subscriptions]({{< relref "/operate/rc/
 
 ### Triggers and functions preview
 
-A preview of [triggers and functions]({{< relref "/operate/oss_and_stack/stack-with-enterprise/triggers-functions" >}}) (previously known as RedisGears) is now available in the following regions:
+A preview of [triggers and functions]({{< relref "/operate/oss_and_stack/stack-with-enterprise/deprecated-features/triggers-and-functions" >}}) (previously known as RedisGears) is now available in the following regions:
 
 - AWS Asia Pacific - Singapore (`ap-southeast-1`)
 - GCP Asia Pacific - Tokyo (`asia-northeast1`)

content/operate/rs/security/certificates/ocsp-stapling.md

@@ -60,7 +60,7 @@ To set up OCSP stapling with the Redis Enterprise Cluster Manager UI:
 
 To set up OCSP stapling with the [REST API]({{< relref "/operate/rs/references/rest-api" >}}):
 
-1. Use the [REST API]({{< relref "/operate/rs/references/rest-api/requests/cluster/update-cert" >}}) to [replace the proxy certificate]({{< relref "/operate/rs/security/certificates/updating-certificates#use-the-rest-api" >}}) with a certificate signed by your third-party CA.
+1. Use the REST API to [replace the proxy certificate]({{< relref "/operate/rs/security/certificates/updating-certificates#use-the-rest-api" >}}) with a certificate signed by your third-party CA.
 
 1. To configure and enable OCSP, send a [`PUT` request to the `/v1/ocsp`]({{< relref "/operate/rs/references/rest-api/requests/ocsp#put-ocsp" >}}) endpoint and include an [OCSP JSON object]({{< relref "/operate/rs/references/rest-api/objects/ocsp" >}}) in the request body: