Skip to content
This repository was archived by the owner on May 10, 2024. It is now read-only.

Commit 07c47e8

Browse files
committed
docs: Fix typo and punctuation in deployment docs
1 parent 4f5c11d commit 07c47e8

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

docs/deployment.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ title: "☁️ Deployment"
44
---
55

66
:::caution Alpha Status
7-
Chroma Server is currently in Alpha. We are working hard to move Chroma from a in-memory single-process oriented library to a distributed production-grade DB!
7+
Chroma Server is currently in Alpha. We are working hard to move Chroma from an in-memory single-process oriented library to a distributed production-grade DB!
88
- [x] Alpha <- Currently
99
- [ ] Technical Preview - ~1 month away, powered by a completely new backend
1010
- [ ] Full production
@@ -21,9 +21,9 @@ provided a very simple AWS CloudFormation template to experiment with
2121
deploying Chroma to EC2 on AWS.
2222

2323
## Hosted Chroma
24-
We want to offer hosted Chroma and we need your help.
24+
We want to offer hosted Chroma, and we need your help.
2525

26-
Fill out the survey to jump the waitlist. Coming Q3 2023.
26+
Fill out the survey to jump the wait-list. Coming Q3 2023.
2727

2828
[📝 30 second survey](https://airtable.com/shrOAiDUtS2ILy5vZ)
2929

@@ -43,7 +43,7 @@ authenticating proxy.
4343

4444
:warning: By default, this template saves all data on a single
4545
volume. When you delete or replace it, the data will disappear. For
46-
serious production use (with high availability, backups, etc) please
46+
serious production use (with high availability, backups, etc.) please
4747
read and understand the CloudFormation template and use it as a basis
4848
for what you need, or reach out to the Chroma team for assistance.
4949

@@ -161,4 +161,4 @@ unless you've taken a snapshot or otherwise backed it up.
161161

162162
### Troubleshooting
163163

164-
If you get an error saying `No default VPC for this user` when creating `ChromaInstanceSecurityGroup`, head to [AWS VPC section]( https://us-east-1.console.aws.amazon.com/vpc/home?region=us-east-1#vpcs) and create deafault VPC for your user
164+
If you get an error saying `No default VPC for this user` when creating `ChromaInstanceSecurityGroup`, head to [AWS VPC section]( https://us-east-1.console.aws.amazon.com/vpc/home?region=us-east-1#vpcs) and create a default VPC for your user.

0 commit comments

Comments
 (0)