DOC-5682 RS: Fixed quote characters

Author: rrelledge

content/operate/rs/7.4/databases/active-active/develop/_index.md

@@ -56,12 +56,12 @@ in between.
 
 |  **Time** | **CRDB Instance1** | **CRDB Instance2** |
 |  ------: | :------: | :------: |
-|  t1 | SET key1 “a” |  |
-|  t2 |  | SET key1 “b” |
+|  t1 | SET key1 "a" |  |
+|  t2 |  | SET key1 "b" |
 |  t3 | — Sync — | — Sync — |
-|  t4 | SET key1 “c” |  |
+|  t4 | SET key1 "c" |  |
 |  t5 | — Sync — | — Sync — |
-|  t6 |  | SET key1 “d” |
+|  t6 |  | SET key1 "d" |
 
 [Learn more about
 synchronization for

content/operate/rs/7.4/databases/active-active/develop/data-types/hashes.md

@@ -37,7 +37,7 @@ Here is an example of an "add wins" case:
 
 |  **Time** | **CRDB Instance1** | **CRDB Instance2** |
 |  ------: | :------: | :------: |
-|  t1 | HSET key1 field1 “a” |  |
-|  t2 |  | HSET key1 field2 “b” |
+|  t1 | HSET key1 field1 "a" |  |
+|  t2 |  | HSET key1 field2 "b" |
 |  t4 | - Sync - | - Sync - |
-|  t5 | HGETALL key1<br/>1) “field2”<br/>2) “b”<br/>3) “field1”<br/>4) “a” | HGETALL key1<br/>1) “field2”<br/>2) “b”<br/>3) “field1”<br/>4) “a” |
+|  t5 | HGETALL key1<br/>1) "field2"<br/>2) "b"<br/>3) "field1"<br/>4) "a" | HGETALL key1<br/>1) "field2"<br/>2) "b"<br/>3) "field1"<br/>4) "a" |

content/operate/rs/7.4/databases/active-active/develop/data-types/lists.md

@@ -27,11 +27,11 @@ example:
 
 |  **Time** | **CRDB Instance 1** | **CRDB Instance 2** |
 |  ------: | :------: | :------: |
-|  t1 | LPUSH mylist “hello” |  |
+|  t1 | LPUSH mylist "hello" |  |
 |  t2 | — Sync — | — Sync — |
-|  t3 |  | LPUSH mylist “world” |
+|  t3 |  | LPUSH mylist "world" |
 |  t4 | — Sync — | — Sync — |
-|  t5 | LRANGE mylist 0 -1 =>“world” “hello” | LRANGE mylist 0 -1 => “world” “hello” |
+|  t5 | LRANGE mylist 0 -1 =>"world" "hello" | LRANGE mylist 0 -1 => "world" "hello" |
 
 **Explanation**:
 The final list contains both the "world" and "hello" elements, in that

content/operate/rs/7.4/databases/active-active/develop/data-types/sets.md

@@ -31,18 +31,18 @@ Here is an example of an "add wins" case:
 
 |  **Time** | **CRDB Instance1** | **CRDB Instance2** |
 |  ------: | :------: | :------: |
-|  t1 | SADD key1 “a” |  |
-|  t2 |  | SADD key1 “b” |
-|  t3 | SMEMBERS key1 “a” | SMEMBERS key1 “b” |
+|  t1 | SADD key1 "a" |  |
+|  t2 |  | SADD key1 "b" |
+|  t3 | SMEMBERS key1 "a" | SMEMBERS key1 "b" |
 |  t4 | — Sync — | — Sync — |
-|  t3 | SMEMBERS key1 “a” “b” | SMEMBERS key1 “a” “b” |
+|  t3 | SMEMBERS key1 "a" "b" | SMEMBERS key1 "a" "b" |
 
 Here is an example of an "observed remove" case.
 
 |  **Time** | **CRDB Instance1** | **CRDB Instance2** |
 |  ------: | :------: | :------: |
-|  t1 | SMEMBERS key1 “a” “b” | SMEMBERS key1 “a” “b” |
-|  t2 | SREM key1 “a” | SADD key1 “c” |
-|  t3 | SREM key1 “c” |  |
+|  t1 | SMEMBERS key1 "a" "b" | SMEMBERS key1 "a" "b" |
+|  t2 | SREM key1 "a" | SADD key1 "c" |
+|  t3 | SREM key1 "c" |  |
 |  t4 | — Sync — | — Sync — |
-|  t3 | SMEMBERS key1 “c” “b” | SMEMBERS key1 “c” “b” |
+|  t3 | SMEMBERS key1 "c" "b" | SMEMBERS key1 "c" "b" |

content/operate/rs/7.4/databases/active-active/develop/data-types/strings.md

@@ -34,12 +34,12 @@ time (t2) wins over the update at t1.
 
 |  **Time** | **Region 1** | **Region 2** |
 |  :------: | :------: | :------: |
-|  t1 | SET text “a” |  |
-|  t2 |  | SET text “b” |
+|  t1 | SET text "a" |  |
+|  t2 |  | SET text "b" |
 |  t3 | — Sync — | — Sync — |
-|  t4 | SET text “c” |  |
+|  t4 | SET text "c" |  |
 |  t5 | — Sync — | — Sync — |
-|  t6 |  | SET text “d” |
+|  t6 |  | SET text "d" |
 
 ### String counter support
 

content/operate/rs/7.4/databases/auto-tiering/_index.md

@@ -53,9 +53,9 @@ When using Auto Tiering, RAM storage holds:
 - Dictionaries
 - Hot data (working set)
 
-All data is accessed through RAM. If a value in flash memory is accessed, it becomes part of the working set and is moved to RAM. These values are referred to as “hot data”.
+All data is accessed through RAM. If a value in flash memory is accessed, it becomes part of the working set and is moved to RAM. These values are referred to as "hot data".
 
-Inactive or infrequently accessed data is referred to as “warm data” and stored in flash memory. When more space is needed in RAM, warm data is moved from RAM to flash storage.
+Inactive or infrequently accessed data is referred to as "warm data" and stored in flash memory. When more space is needed in RAM, warm data is moved from RAM to flash storage.
 
 {{<note>}} When using Auto Tiering with RediSearch, it’s important to note that RediSearch indexes are also stored in RAM.{{</note>}}
 

content/operate/rs/7.4/installing-upgrading/product-lifecycle.md

@@ -19,7 +19,7 @@ Redis Enterprise modules follow the [modules lifecycle]({{< relref "/operate/oss
 ## Release numbers
 
 Redis uses a four-place numbering scheme to designate released versions of its products.
-The format is “Major1.Major2.Minor-Build”.
+The format is "Major1.Major2.Minor-Build".
 
 - Major sections of the version number represents fundamental changes and additions in
     capabilities to Redis  Enterprise Software. The Major1 and Major2 part of the

content/operate/rs/7.4/networking/cluster-lba-setup.md

@@ -44,7 +44,7 @@ The architecture is shown in the following diagram with a 3-node Redis Enterpris
 - [Install]({{< relref "/operate/rs/7.4/installing-upgrading" >}}) the latest version of Redis Enterprise Software on your clusters
 - Configure the cluster with the cluster name (FQDN) even though DNS is not in use.
     Remember that the same cluster name is used to issue the license keys.
-    We recommend that you use a “.local” suffix in the FQDN.
+    We recommend that you use a ".local" suffix in the FQDN.
 
 ### Configure load balancers
 

content/operate/rs/7.4/references/rest-api/requests/bdbs/modules/config.md

@@ -61,7 +61,7 @@ Use the module runtime configuration command (if defined) to configure new argum
 |-------|------|-------------|
 | modules | list of JSON objects | List of modules (module_name) and their new configuration settings (module_args) |
 | module_name | `search`<br />`ReJSON`<br />`graph`<br />`timeseries`<br />`bf` | Module's name |
-| module_args | string | Module command line arguments (pattern does not allow special characters &,<,>,”) |
+| module_args | string | Module command line arguments (pattern does not allow special characters &,<,>,") |
 
 ### Response {#post-response} 
 

content/operate/rs/7.4/references/rest-api/requests/modules/config.md

@@ -61,7 +61,7 @@ Use the module runtime configuration command (if defined) to configure new argum
 |-------|------|-------------|
 | modules | list of JSON objects | List of modules (module_name) and their new configuration settings (module_args) |
 | module_name | `search`<br />`ReJSON`<br />`graph`<br />`timeseries`<br />`bf` | Module's name |
-| module_args | string | Module command line arguments (pattern does not allow special characters &,<,>,”) |
+| module_args | string | Module command line arguments (pattern does not allow special characters &,<,>,") |
 
 ### Response {#post-response}