From 7b406c647cb6e8f65659539aec145453dd1b9d91 Mon Sep 17 00:00:00 2001 From: flip111 Date: Fri, 29 Nov 2019 15:59:42 +0100 Subject: [PATCH] Update compilation.rst fixed two spelling mistakes --- doc/dev-reference/compilation.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/dev-reference/compilation.rst b/doc/dev-reference/compilation.rst index 93290467..a2eee106 100644 --- a/doc/dev-reference/compilation.rst +++ b/doc/dev-reference/compilation.rst @@ -75,12 +75,12 @@ characters exist in regular grammer like ``[``, ``]``, ``(``, ``)``, ``{``, While in pure literal case, all these meta characters lost extra meanings expect for that they are just common ASCII codes. -Hyperscan is initially designed to process common regualr expressions. It is +Hyperscan is initially designed to process common regular expressions. It is hence embedded with a complex parser to do comprehensive regular grammer interpretion. Particularly, the identification of above meta characters is the basic step for the interpretion of far more complex regular grammers. -However in real cases, patterns may not always be regualr expressions. They +However in real cases, patterns may not always be regular expressions. They could just be pure literals. Problem will come if the pure literals contain regular meta characters. Supposing fed directly into traditional Hyperscan compile API, all these meta characters will be interpreted in predefined ways,