From a2444fe93e036293d6c8637f0c902e81a54d8232 Mon Sep 17 00:00:00 2001 From: Josh Bodah Date: Thu, 29 Sep 2016 16:17:59 -0400 Subject: [PATCH] fix doc spelling --- doc/throttle.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/throttle.md b/doc/throttle.md index 8c28f01..10d38d1 100644 --- a/doc/throttle.md +++ b/doc/throttle.md @@ -46,7 +46,7 @@ Note that you may dynamically change both `replication-lag-query` and the `throt `--max-load='Threads_running=100,Threads_connected=500'` - Metrics must be valid, numeric [statis variables](http://dev.mysql.com/doc/refman/5.6/en/server-status-variables.html) + Metrics must be valid, numeric [status variables](http://dev.mysql.com/doc/refman/5.6/en/server-status-variables.html) #### Throttle query @@ -80,7 +80,7 @@ In addition to the above, you are able to take control and throttle the operatio Any single factor in the above that suggests the migration should throttle - causes throttling. That is, once some component decides to throttle, you cannot override it; you cannot force continued execution of the migration. -`gh-ost` collects different throttle-related metrics at different times, independently. It asynchronously reads the collected metrics and checks if they satisfy conditions/threasholds. +`gh-ost` collects different throttle-related metrics at different times, independently. It asynchronously reads the collected metrics and checks if they satisfy conditions/thresholds. The first check to suggest throttling stops the check; the status message will note the reason for throttling as the first satisfied check.