From 2d869ae0a41d6b1181b632614e01fff8fd2ed2ef Mon Sep 17 00:00:00 2001 From: SataQiu Date: Mon, 15 Apr 2019 17:34:41 +0800 Subject: [PATCH] fix spelling errors of doc/VitessSequences.md doc/VitessTransportSecurityModel.md Signed-off-by: SataQiu --- doc/VitessSequences.md | 2 +- doc/VitessTransportSecurityModel.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/VitessSequences.md b/doc/VitessSequences.md index d2a68ceb4ad..155b315acfb 100644 --- a/doc/VitessSequences.md +++ b/doc/VitessSequences.md @@ -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 diff --git a/doc/VitessTransportSecurityModel.md b/doc/VitessTransportSecurityModel.md index a0df28cc11b..bc9d0ebe832 100644 --- a/doc/VitessTransportSecurityModel.md +++ b/doc/VitessTransportSecurityModel.md @@ -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.