minor updates

trimstray · trimstray · commit d73e1e5b95c2 · 2020-09-10T07:05:11.000+02:00
- signed-off-by: trimstray &lt;trimstray@gmail.com&gt;
diff --git a/doc/NGINX_BASICS.md b/doc/NGINX_BASICS.md
@@ -2103,6 +2103,10 @@ The `ngx_http_rewrite_module` also provides additional directives:
 
   > _That’s actually not true and shows you don’t understand the problem with it. When the `if` statement ends with `return` directive, there is no problem and it’s safe to use._
 
+  On the other hand, official documentation say:
+
+  > _Directive if has problems when used in location context, in some cases it doesn’t do what you expect but something completely different instead. In some cases it even segfaults. It’s generally a good idea to avoid it if possible._
+
 - `set` - sets a value for the specified variable. The value can contain text, variables, and their combination
 
 Example of usage `if` and `set` directives:
diff --git a/doc/RULES.md b/doc/RULES.md
@@ -1911,12 +1911,16 @@ server {
 
 ###### Rationale
 
-  > When NGINX receives a request no matter what is the subdomain being requested, be it `www.example.com` or just the plain `example.com` this `if` directive is always evaluated. Since you’re requesting NGINX to check for the `Host` header for every request. It’s extremely inefficient.
+  > When NGINX receives a request no matter what is the subdomain being requested, be it `www.example.com` or just the plain `example.com` this `if` directive is always evaluated. Since you’re requesting NGINX to check for the `Host` header for every request. It might be extremely inefficient.
 
   > Instead use two server directives like the example below. This approach decreases NGINX processing requirements.
 
   > The problem is not just the `$server_name` directive. Keep in mind also other variables, e.g. `$scheme`. In some cases (but not always), it is better to add an additional block directive than to use the `if`.
 
+  On the other hand, official documentation say:
+
+  > _Directive if has problems when used in location context, in some cases it doesn’t do what you expect but something completely different instead. In some cases it even segfaults. It’s generally a good idea to avoid it if possible._
+
 ###### Example
 
 Not recommended configuration:
