From b7c3e2fafd221b6e1795d75ae629e696d522f1e4 Mon Sep 17 00:00:00 2001 From: Manan Gupta Date: Thu, 22 Dec 2022 10:29:37 +0530 Subject: [PATCH] feat: fix count of bullets Signed-off-by: Manan Gupta --- content/en/docs/15.0/concepts/query-rewriting.md | 2 +- content/en/docs/16.0/concepts/query-rewriting.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/15.0/concepts/query-rewriting.md b/content/en/docs/15.0/concepts/query-rewriting.md index a0eddee93..8476c51c2 100644 --- a/content/en/docs/15.0/concepts/query-rewriting.md +++ b/content/en/docs/15.0/concepts/query-rewriting.md @@ -58,7 +58,7 @@ This way, no session state is needed to evaluate the query in MySQL. ### Server System Variables A user might also want to change one of the many different system variables that MySQL exposes. -Vitess handles system variables in one of four different ways: +Vitess handles system variables in one of five different ways: * *No op*. For some settings, Vitess will just silently ignore the setting. This is for system variables that don't make much sense in a sharded setting, and don't change the behaviour of MySQL in an interesting way. * *Check and fail if not already set*. These are settings that should not change, but Vitess will allow SET statements that try to set the variable to whatever it already is. diff --git a/content/en/docs/16.0/concepts/query-rewriting.md b/content/en/docs/16.0/concepts/query-rewriting.md index a8181e521..f167eab3d 100644 --- a/content/en/docs/16.0/concepts/query-rewriting.md +++ b/content/en/docs/16.0/concepts/query-rewriting.md @@ -58,7 +58,7 @@ This way, no session state is needed to evaluate the query in MySQL. ### Server System Variables A user might also want to change one of the many different system variables that MySQL exposes. -Vitess handles system variables in one of four different ways: +Vitess handles system variables in one of five different ways: * *No op*. For some settings, Vitess will just silently ignore the setting. This is for system variables that don't make much sense in a sharded setting, and don't change the behaviour of MySQL in an interesting way. * *Check and fail if not already set*. These are settings that should not change, but Vitess will allow SET statements that try to set the variable to whatever it already is.