Copied Redis Open Source name to RS 7.8 version

Author: rrelledge

content/operate/rs/7.8/_index.md

@@ -75,7 +75,7 @@ To view documentation earlier than version 7.4, see the archived website:
 
 ## Related info
 - [Redis Cloud]({{< relref "/operate/rc" >}})
-- [Redis Community Edition]({{< relref "/operate/oss_and_stack" >}})
+- [Redis Open Source]({{< relref "/operate/oss_and_stack" >}})
 - [Redis Stack]({{< relref "/operate/oss_and_stack/stack-with-enterprise" >}})
 - [Glossary]({{< relref "/glossary" >}})
 

content/operate/rs/7.8/databases/active-active/develop/data-types/hyperloglog.md

@@ -18,7 +18,7 @@ Because it estimates the cardinality by probability, the HyperLogLog algorithm c
 
 ## HyperLogLog in Redis
 
-Redis Community Edition implements [HyperLogLog](https://redislabs.com/redis-best-practices/counting/hyperloglog/) (HLL) as a native data structure.
+Redis Open Source implements [HyperLogLog](https://redislabs.com/redis-best-practices/counting/hyperloglog/) (HLL) as a native data structure.
 It supports adding elements ([PFADD]({{< relref "/commands/pfadd" >}}) to an HLL, counting elements ([PFCOUNT]({{< relref "/commands/pfcount" >}}) of HLLs, and merging of ([PFMERGE]({{< relref "/commands/pfmerge" >}}) HLLs.
 
 Here is an example of a simple write case:
@@ -48,7 +48,7 @@ If a DEL request is received at the same time as any other request (ADD/MERGE/EX
 the replicas consistently converge to delete key.
 In the observed remove method used by other collections (sets, lists, sorted-sets and hashes),
 only the replica that received the DEL request removes the elements, but elements added concurrently in other replicas exist in the consistently converged collection.
-We chose to use the DEL-wins method for the CRDT-HLL to maintain the original time and space complexity of the HLL in Redis Community Edition.
+We chose to use the DEL-wins method for the CRDT-HLL to maintain the original time and space complexity of the HLL in Redis Open Source.
 
 Here is an example of a DEL-wins case:
 
@@ -67,7 +67,7 @@ Here is an example of a DEL-wins case:
 | t8   | Exists h --> 0  | Exists h --> 0  | \|  | t8   | Exists s --> 1      | Exists s --> 1      |
 |      |                 |                 | \|  | t9   | SMEMBERS s --> {e2} | SMEMBERS s --> {e2} |
 
-## HLL in Active-Active databases versus HLL in Redis Community Edition
+## HLL in Active-Active databases versus HLL in Redis Open Source
 
 In Active-Active databases, we implemented HLL within the CRDT on the basis of the Redis implementation with a few exceptions:
 

content/operate/rs/7.8/databases/active-active/develop/data-types/streams.md

@@ -65,7 +65,7 @@ In the example below, we write to a stream concurrently from two regions. Notice
 Notice also that the synchronized streams contain no duplicate IDs. As long as you allow the database to generate your stream IDs, you'll never have more than one stream entry with the same ID.
 
 {{< note >}}
-Redis Community Edition uses one radix tree (referred to as `rax` in the code base) to implement each stream. However, Active-Active databases implement a single logical stream using one `rax` per region.
+Redis Open Source uses one radix tree (referred to as `rax` in the code base) to implement each stream. However, Active-Active databases implement a single logical stream using one `rax` per region.
 Each region adds entries only to its associated `rax` (but can remove entries from all `rax` trees).
 This means that XREAD and XREADGROUP iterate simultaneously over all `rax` trees and return the appropriate entry by comparing the entry IDs from each `rax`.
 {{< /note >}}
@@ -147,7 +147,7 @@ Because Active-Active databases replicate asynchronously, providing your own IDs
 In this scenario, two entries with the ID `100-1` are added at _t1_. After syncing, the stream `x` contains two entries with the same ID.
 
 {{< note >}}
-Stream IDs in Redis Community Edition consist of two integers separated by a dash ('-'). When the server generates the ID, the first integer is the current time in milliseconds, and the second integer is a sequence number. So, the format for stream IDs is MS-SEQ.
+Stream IDs in Redis Open Source consist of two integers separated by a dash ('-'). When the server generates the ID, the first integer is the current time in milliseconds, and the second integer is a sequence number. So, the format for stream IDs is MS-SEQ.
 {{< /note >}}
 
 To prevent duplicate IDs and to comply with the original Redis streams design, Active-Active databases provide three ID modes for XADD:
@@ -181,7 +181,7 @@ rladmin tune db crdb crdt_xadd_id_uniqueness_mode liberal
 
 ### Iterating a stream with XREAD
 
-In Redis Community Edition and in non-Active-Active databases, you can use XREAD to iterate over the entries in a Redis Stream. However, with an Active-Active database, XREAD may skip entries. This can happen when multiple regions write to the same stream.
+In Redis Open Source and in non-Active-Active databases, you can use XREAD to iterate over the entries in a Redis Stream. However, with an Active-Active database, XREAD may skip entries. This can happen when multiple regions write to the same stream.
 
 In the example below, XREAD skips entry `115-2`.
 
@@ -211,7 +211,7 @@ Active-Active databases fully support consumer groups with Redis Streams. Here i
 
 
 {{< note >}}
-Redis Community Edition uses one radix tree (`rax`) to hold the global pending entries list and another `rax` for each consumer's PEL.
+Redis Open Source uses one radix tree (`rax`) to hold the global pending entries list and another `rax` for each consumer's PEL.
 The global PEL is a unification of all consumer PELs, which are disjoint.
 
 An Active-Active database stream maintains a global PEL and a per-consumer PEL for each region.
@@ -302,7 +302,7 @@ In traffic redirection, XREADGROUP may return entries that have been read but no
 
 ## Summary
 
-With Active-Active streams, you can write to the same logical stream from multiple regions. As a result, the behavior of Active-Active streams differs somewhat from the behavior you get with Redis Community Edition. This is summarized below:
+With Active-Active streams, you can write to the same logical stream from multiple regions. As a result, the behavior of Active-Active streams differs somewhat from the behavior you get with Redis Open Source. This is summarized below:
 
 ### Stream commands
 

content/operate/rs/7.8/databases/active-active/syncer.md

@@ -21,7 +21,7 @@ The syncer process:
 1. Reads data from that database instance
 1. Writes the data to the local cluster's primary(master) shard
 
-Some replication capabilities are also included in [Redis Community Edition]({{< relref "/operate/oss_and_stack/management/replication" >}}).
+Some replication capabilities are also included in [Redis Open Source]({{< relref "/operate/oss_and_stack/management/replication" >}}).
 
 The primary (also known as master) shard at the top of the primary-replica tree creates a replication ID.
 This replication ID is identical for all replicas in that tree.

content/operate/rs/7.8/databases/configure/_index.md

@@ -23,7 +23,7 @@ You can manage your Redis Enterprise Software databases with several tools:
 
     - [`crdb-cli`]({{< relref "/operate/rs/7.8/references/cli-utilities/crdb-cli" >}}) for Active-Active database configuration
 
-    - [`redis-cli`]({{< relref "/develop/tools/cli" >}}) for Redis Community Edition configuration
+    - [`redis-cli`]({{< relref "/develop/tools/cli" >}}) for Redis Open Source configuration
 
 - [REST API]({{< relref "/operate/rs/7.8/references/rest-api/_index.md" >}})
 
@@ -142,7 +142,7 @@ To change capabilities' parameters for an existing database using the Cluster Ma
 You must use a client that supports the cluster API to connect to a database that has the cluster API enabled.
     {{</note>}}
 
-- **Hashing policy** - You can accept the [standard hashing policy]({{<relref "/operate/rs/7.8/databases/durability-ha/clustering#standard-hashing-policy">}}), which is compatible with Redis Community Edition, or define a [custom hashing policy]({{<relref "/operate/rs/7.8/databases/durability-ha/clustering#custom-hashing-policy">}}) to define where keys are located in the clustered database.
+- **Hashing policy** - You can accept the [standard hashing policy]({{<relref "/operate/rs/7.8/databases/durability-ha/clustering#standard-hashing-policy">}}), which is compatible with Redis Open Source, or define a [custom hashing policy]({{<relref "/operate/rs/7.8/databases/durability-ha/clustering#custom-hashing-policy">}}) to define where keys are located in the clustered database.
 
 - [**Database proxy**]({{< relref "/operate/rs/7.8/databases/configure/proxy-policy" >}}) - Determines the number and location of active proxies, which manage incoming database operation requests.
 

content/operate/rs/7.8/databases/durability-ha/clustering.md

@@ -62,7 +62,7 @@ is 3, you can increase the number of shards to 6, 9, or 12.
 
 ### Standard hashing policy
 
-When using the standard hashing policy, a clustered Redis Enterprise database behaves similarly to a standard [Redis Community Edition cluster]({{< relref "/operate/oss_and_stack/reference/cluster-spec" >}}#hash-tags), except when using multiple hash tags in a key's name. We recommend using only a single hash tag in a key name for hashing in Redis Enterprise.
+When using the standard hashing policy, a clustered Redis Enterprise database behaves similarly to a standard [Redis Open Source cluster]({{< relref "/operate/oss_and_stack/reference/cluster-spec" >}}#hash-tags), except when using multiple hash tags in a key's name. We recommend using only a single hash tag in a key name for hashing in Redis Enterprise.
 
 - **Keys with a hash tag**: a key's hash tag is any substring between
     `{` and `}` in the key's name. When a key's name

content/operate/rs/7.8/databases/import-export/migrate-to-active-active.md

@@ -102,9 +102,9 @@ To migrate a database to Active-Active in different Redis Enterprise clusters:
 
 1. Click **Save**.
 
-## Migrate from Redis Community Edition
+## Migrate from Redis Open Source
 
-To migrate a Redis Community Edition database to Active-Active:
+To migrate a Redis Open Source database to Active-Active:
 
 1. Create a new Active-Active database. For prerequisites and detailed instructions, see [Create an Active-Active geo-replicated database]({{< relref "/operate/rs/7.8/databases/active-active/create" >}}).
 

content/operate/rs/7.8/databases/import-export/replica-of/create.md

@@ -19,7 +19,7 @@ Sources databases can be:
 - Located in the same Redis Enterprise Software cluster
 - Located in a different Redis Enterprise cluster
 - Hosted by a different deployment, e.g. Redis Cloud
-- Redis Community Edition databases
+- Redis Open Source databases
 
 Your apps can connect to the source database to read and write data; they can also use any replica for read-only access.
 
@@ -38,7 +38,7 @@ You can configure a database as a Replica Of, where the source database is in on
 
 - [Different Redis Enterprise cluster](#different-cluster)
 
-- [Redis Community Edition cluster](#source-available-cluster)
+- [Redis Open Source cluster](#source-available-cluster)
 
 The order of the multiple Replica Of sources has no material impact on replication.
 
@@ -106,9 +106,9 @@ To configure a Replica Of database in a different Redis Enterprise cluster from
 
 For source databases on different clusters, you can [compress replication data]({{< relref "/operate/rs/7.8/databases/import-export/replica-of/#data-compression-for-replica-of" >}}) to save bandwidth.
 
-### Redis Community Edition cluster {#source-available-cluster}
+### Redis Open Source cluster {#source-available-cluster}
 
-To use a database from a Redis Community Edition cluster as a Replica Of source:
+To use a database from a Redis Open Source cluster as a Replica Of source:
 
 1. [Create a new database]({{< relref "/operate/rs/7.8/databases/create" >}}) or select an existing database from the **Databases** screen.
 

content/operate/rs/7.8/networking/cluster-dns.md

@@ -11,7 +11,7 @@ weight: $weight
 url: '/operate/rs/7.8/networking/cluster-dns/'
 ---
 
-By default, Redis Enterprise Software deployments use DNS to communicate between nodes.  You can also use the [Discovery Service]({{< relref "/operate/rs/7.8/databases/durability-ha/discovery-service.md" >}}), which uses IP addresses to connect and complies with the [Redis Sentinel API]({{< relref "/operate/oss_and_stack/management/sentinel" >}}) supported by Redis Community Edition.
+By default, Redis Enterprise Software deployments use DNS to communicate between nodes.  You can also use the [Discovery Service]({{< relref "/operate/rs/7.8/databases/durability-ha/discovery-service.md" >}}), which uses IP addresses to connect and complies with the [Redis Sentinel API]({{< relref "/operate/oss_and_stack/management/sentinel" >}}) supported by Redis Open Source.
 
 Each node in a Redis Enterprise cluster includes a small DNS server to manage internal functions, such as high availability, automatic failover, automatic migration, and so on.
 Nodes should only run the DNS server included with the software.  Running additional DNS servers can lead to unexpected behavior.

content/operate/rs/7.8/references/cli-utilities/redis-cli/_index.md

@@ -20,11 +20,11 @@ If you want to run Redis commands without `redis-cli`, you can [connect to a dat
 
 ## Install `redis-cli`
 
-When you install Redis Enterprise Software or Redis Community Edition, it also installs the `redis-cli` command-line utility.
+When you install Redis Enterprise Software or Redis Open Source, it also installs the `redis-cli` command-line utility.
 
 To learn how to install Redis and `redis-cli`, see the following installation guides:
 
-- [Redis Community Edition]({{< relref "/operate/oss_and_stack/install/install-redis/" >}})
+- [Redis Open Source]({{< relref "/operate/oss_and_stack/install/install-stack/" >}})
 
 - [Redis Enterprise Software]({{< relref "/operate/rs/7.8/installing-upgrading/quickstarts/redis-enterprise-software-quickstart" >}})