|
39 | 39 | * [5.3. Enabling Redo Operation](#53-enabling-redo-operation) |
40 | 40 | * [5.4. Setting Connection Timeout](#54-setting-connection-timeout) |
41 | 41 | * [5.5. Enabling Client TLS/SSL](#55-enabling-client-tlsssl) |
42 | | - * [5.6. Enabling Hazelcast Viridian Discovery](#56-enabling-hazelcast-viridian-discovery) |
| 42 | + * [5.6. Enabling Hazelcast Cloud Discovery](#56-enabling-hazelcast-cloud-discovery) |
43 | 43 | * [5.7. Configuring Backup Acknowledgment](#57-configuring-backup-acknowledgment) |
44 | 44 | * [5.8. External Client Public Address Discovery](#58-external-client-public-address-discovery) |
45 | 45 | * [6. Client Connection Strategy](#6-client-connection-strategy) |
@@ -699,19 +699,19 @@ When Hazelcast Node.js client serializes an object: |
699 | 699 |
|
700 | 700 | 4. If the above check fails, then it checks if it is an instance of one of the default types (see above default types). |
701 | 701 |
|
702 | | -5. If the above check fails, then it looks for a user-specified [Custom Serialization](#43-custom-serialization). |
| 702 | +5. If the above check fails, then it looks for a user-specified [Custom Serialization](#44-custom-serialization). |
703 | 703 |
|
704 | | -6. If the above check fails, it will use the registered [Global Serialization](#44-global-serialization) if one exists. |
| 704 | +6. If the above check fails, it will use the registered [Global Serialization](#45-global-serialization) if one exists. |
705 | 705 |
|
706 | 706 | 7. If the above check fails, then the Node.js client uses `JSON Serialization` by default. |
707 | 707 |
|
708 | 708 | However, `JSON Serialization` may not be the best way of serialization in terms of performance and interoperability between |
709 | 709 | the clients in different languages. If you want the serialization to work faster or you use the clients in different languages, |
710 | 710 | Hazelcast offers its own native serialization methods, such as |
711 | | -[`IdentifiedDataSerializable` Serialization](#41-identifieddataserializable-serialization) and |
712 | | -[`Portable` Serialization](#42-portable-serialization). |
| 711 | +[`IdentifiedDataSerializable` Serialization](#42-identifieddataserializable-serialization) and |
| 712 | +[`Portable` Serialization](#43-portable-serialization). |
713 | 713 |
|
714 | | -Or, if you want to use your own serialization method, you can use [Custom Serialization](#43-custom-serialization). |
| 714 | +Or, if you want to use your own serialization method, you can use [Custom Serialization](#44-custom-serialization). |
715 | 715 |
|
716 | 716 | > **NOTE: Hazelcast Node.js client is a TypeScript-based project but JavaScript does not have interfaces. Therefore, some |
717 | 717 | > interfaces are given to the user by using the TypeScript files that have `.ts` extension. In this guide, implementing an |
@@ -1431,10 +1431,10 @@ authentication feature which allows the Node.js clients also to have their priva |
1431 | 1431 | to have their certificate authorities so that the members can know which clients they can trust. See the |
1432 | 1432 | [Mutual Authentication section](#913-mutual-authentication). |
1433 | 1433 |
|
1434 | | -## 5.6. Enabling Hazelcast Viridian Discovery |
| 1434 | +## 5.6. Enabling Hazelcast Cloud Discovery |
1435 | 1435 |
|
1436 | 1436 | Hazelcast Node.js client can discover and connect to Hazelcast clusters running on |
1437 | | -[Hazelcast Viridian](https://viridian.hazelcast.com/). For this, provide authentication information as `clusterName` and enable cloud |
| 1437 | +[Hazelcast Cloud](https://cloud.hazelcast.com/). For this, provide authentication information as `clusterName` and enable cloud |
1438 | 1438 | discovery by setting your `discoveryToken` as shown below. |
1439 | 1439 |
|
1440 | 1440 | ```javascript |
@@ -3567,7 +3567,7 @@ results of your query are ready, they are parsed from JSON strings and returned |
3567 | 3567 |
|
3568 | 3568 | For the purposes of your application, you may want to get rid of the parsing and just work with the raw JSON strings using |
3569 | 3569 | `HazelcastJsonValue` objects. Then, you can configure your client to do so as described in the |
3570 | | -[JSON Serialization](#45-json-serialization) section. |
| 3570 | +[JSON Serialization](#46-json-serialization) section. |
3571 | 3571 |
|
3572 | 3572 | ```javascript |
3573 | 3573 | const client = await Client.newHazelcastClient({ |
|
0 commit comments