Skip to content

Commit 30a6207

Browse files
Apply suggestions from code review
Co-authored-by: Spike Curtis <spike@coder.com>
1 parent fbedc4e commit 30a6207

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/tutorials/best-practices/scale-coder.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Scale Coder
22

3-
This best practice guide helps you prepare a low-scale Coder deployment that you can
3+
This best practice guide helps you prepare a Coder deployment that you can
44
scale up to a high-scale deployment as use grows, and keep it operating smoothly with a
55
high number of active users and workspaces.
66

@@ -249,11 +249,11 @@ size of the cluster, especially in the case of a private cloud, or soft limits,
249249
based on configured limits in your public cloud account.
250250

251251
It is important to be aware of these limits and monitor Coder workspace resource
252-
utilization against the limits, so that a new influx of users doesn't encounter
252+
utilization against the limits, so that a new influx of users don't encounter
253253
failed builds. Monitoring these is outside the scope of Coder, but we recommend
254254
that you set up dashboards and alerts for each kind of limited resource.
255255

256-
As you approach soft limits, you can increase limits to keep growing.
256+
As you approach soft limits, you can request limit increases to keep growing.
257257

258258
As you approach hard limits, consider deploying to additional cluster(s).
259259

0 commit comments

Comments
 (0)