Skip to content

Commit ece2d47

Browse files
committed
Admin/Performance: Implement suggestions by CodeRabbit
1 parent 5a834de commit ece2d47

File tree

2 files changed

+6
-8
lines changed

2 files changed

+6
-8
lines changed

docs/admin/index.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ circuit-breaker
2323
troubleshooting/index
2424
```
2525
+++
26-
Production and troubleshooting guidelines, and system resource considerations.
26+
Production and troubleshooting guidelines and system resource considerations.
2727
::::
2828

2929
::::{grid-item-card} {material-outlined}`speed;2em` Cluster
@@ -35,8 +35,7 @@ sharding-partitioning
3535
../performance/index
3636
```
3737
+++
38-
Best practices and tips around the topics of
39-
clustering, sharding, partitioning, and performance tuning.
38+
Best practices and tips for clustering, sharding, partitioning, and performance tuning.
4039
::::
4140

4241
::::{grid-item-card} {material-outlined}`system_update_alt;2em` Software Upgrades
@@ -46,8 +45,7 @@ clustering, sharding, partitioning, and performance tuning.
4645
upgrade/index
4746
```
4847
+++
49-
Guidelines about upgrading CrateDB clusters in production,
50-
from planning to execution.
48+
Guidelines for upgrading CrateDB clusters in production—from planning to execution.
5149
::::
5250

5351
:::::

docs/performance/index.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -33,9 +33,9 @@ selects
3333
optimization
3434
```
3535
+++
36-
Design SQL statements for maximum performance and lower resource usage.
37-
Applicable when latency matters, or when a resource‑heavy query could
38-
overload your cluster.
36+
Design SQL statements for maximum performance and reduced resource usage.
37+
Use when latency matters or when a resource‑heavy query could overload
38+
your cluster.
3939
::::
4040

4141
:::::

0 commit comments

Comments
 (0)