Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix spelling errors of doc/VitessSequences.md doc/VitessTransportSecurityModel.md #4808

Merged
merged 1 commit into from
Apr 15, 2019
Merged

Fix spelling errors of doc/VitessSequences.md doc/VitessTransportSecurityModel.md #4808

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion doc/VitessSequences.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -87,7 +87,7 @@ Let's start by looking at the MySQL auto-increment feature:

An early design was to use a single unsharded database and a table with an
auto-increment value to generate new values. However, this has serious
limitations, in particular throughtput, and storing one entry for each value in
limitations, in particular throughput, and storing one entry for each value in
that table, for no reason.

So we decided instead to base sequences on a MySQL table, and use a single value
Expand Down
2 changes: 1 addition & 1 deletion doc/VitessTransportSecurityModel.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ When using gRPC transport, Vitess can use the usual TLS security features
* grpc\_cert, grpc\_key: server cert and key to use.
* grpc\_ca (optional): client cert chains to trust. If specified, the client
must use a certificate signed by one ca in the provided file.
* A Vitess go client can be configured with symetrical parameters to enable TLS:
* A Vitess go client can be configured with symmetrical parameters to enable TLS:
* ...\_grpc\_ca: list of server cert signers to trust.
* ...\_grpc\_server\_name: name of the server cert to trust, instead of the
hostname used to connect.
Expand Down