krzysztof/landing_page
1
0
Fork 0
mirror of https://github.com/qdrant/landing_page.git synced 2026-10-07 11:58:31 +02:00
Code Issues Packages Projects Releases Wiki Activity

Fix Docs : minor grammar fixes (#2218)

Browse Source 
* fix(docs): fix typos and some links in documentation

* fix(docs): correct typo in filtering.md

* Update qdrant-landing/content/documentation/headless/snippets/inference/jinaai-upsert/generated/typescript.md

Co-authored-by: Abdon Pijpelink <abdon.pijpelink@qdrant.com>

* Update qdrant-landing/content/documentation/headless/snippets/inference/multiple/generated/typescript.md

Co-authored-by: Abdon Pijpelink <abdon.pijpelink@qdrant.com>

* Update qdrant-landing/content/documentation/hybrid-cloud/configure-scale-upgrade.md

Co-authored-by: Abdon Pijpelink <abdon.pijpelink@qdrant.com>

* Update qdrant-landing/content/documentation/cloud-api.md

Co-authored-by: Abdon Pijpelink <abdon.pijpelink@qdrant.com>

---------

Co-authored-by: Abdon Pijpelink <abdon.pijpelink@qdrant.com>
This commit is contained in:
Mohamed Arbi
2026-03-26 17:23:36 +01:00
committed by GitHub
co-authored by Abdon Pijpelink
parent 3f3ef1ad20
commit c0db45ed8f
58 changed files with 75 additions and 75 deletions
Download Patch File Download Diff File Expand all files Collapse all files
qdrant-landing/content/documentation/operations/distributed_deployment.md
+3 -3
View File
@@ -305,10 +305,10 @@ If you anticipate a lot of growth, we recommend 12 shards since you can expand f
Shards are evenly distributed across all existing nodes when a collection is first created.
When you add or remove nodes from the cluster, rebalancing of existing shards accross the nodes depends on how you've deployed the cluster:
When you add or remove nodes from the cluster, rebalancing of existing shards across the nodes depends on how you've deployed the cluster:
- In Qdrant Cloud, shards are [balanced across the nodes automatically](/documentation/cloud/configure-cluster/#shard-rebalancing).
- If your cluster is not runnning in Qdrant Cloud, you need to [manually balance shards](#moving-shards).
- If your cluster is not running in Qdrant Cloud, you need to [manually balance shards](#moving-shards).
### Resharding
@@ -1326,7 +1326,7 @@ Listener node will not participate in search operations, but will still accept w
All shards, stored on the listener node, will be converted to the `Listener` state.
Additionally, all write requests sent to the listener node will be processed with `wait=false` option, which means that the write oprations will be considered successful once they are written to WAL.
Additionally, all write requests sent to the listener node will be processed with `wait=false` option, which means that the write operations will be considered successful once they are written to WAL.
This mechanism should allow to minimize upsert latency in case of parallel snapshotting.
## Consensus Checkpointing
qdrant-landing/content/documentation/operations/usage-statistics.md
+1 -1
View File
@@ -11,7 +11,7 @@ aliases:
The Qdrant open-source container image collects anonymized usage statistics from users in order to improve the engine by default. You can [deactivate](#deactivate-telemetry) at any time, and any data that has already been collected can be [deleted on request](#request-information-deletion).
Deactivating this will not affect your ability to monitor the Qdrant database yourself by accessing the `/metrics` or `/telemetry` endpoints of your database. It will just stop sending independend, anonymized usage statistics to the Qdrant team.
Deactivating this will not affect your ability to monitor the Qdrant database yourself by accessing the `/metrics` or `/telemetry` endpoints of your database. It will just stop sending independent, anonymized usage statistics to the Qdrant team.
<aside role="status">When using Qdrant Cloud, this setting does not apply and anonymized usage statistics are disabled by default.</aside>