From 3160dd30c06d12a74cea4675c7947a95cfeba3a3 Mon Sep 17 00:00:00 2001
From: paveld <37961802+pavepp@users.noreply.github.com>
Date: Thu, 11 Jun 2020 17:56:34 +0200
Subject: [PATCH] edited the grep section

a fair amount of the special characters didnt seem to work for me, did some research and.. BRE and ERE were a bit mixed up
---
 shell_tools_101.rst | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/shell_tools_101.rst b/shell_tools_101.rst
index 575bdda1..cb34e932 100644
--- a/shell_tools_101.rst
+++ b/shell_tools_101.rst
@@ -448,7 +448,9 @@ Characters      Meaning
 Note that there's almost always more than one way to express a particular pattern. 
 When you're developing a regular expression, it can be helpful to test it on simplified input to see what it catches.
 To test a regex for various spellings of opsschool, you might put a variety of spellings in a file and then grep it to see which regex catches which spellings.
-
+Lastly, there is a big difference between a plain ``grep`` call and a ``grep -E`` call (Basic RE vs. Extended RE). In BRE, any of these characters need a preceding backslash in order for them to take effect: {}, +, ?, |
+If not preceded by a backslash they are treated as normal characters.
+E.g. ``grep "ops \?school"`` is equivalent to ``grep -E "ops ?school"``
 .. code-block:: console
 
     user@opsschool ~$ cat ops.txt