s/interprete/interpret/

README.md

@@ -156,13 +156,13 @@ the possible constructions.
 Now, we have two options to save the rule, for example, in a database. Either we
 save the rule as a string directly, or we will save the serialization of the
 rule which will avoid further interpretations. In the next example, we see how
-to serialize and unserialize a rule by using the `Hoa\Ruler\Ruler::interprete`
+to serialize and unserialize a rule by using the `Hoa\Ruler\Ruler::interpret`
 static method:
 
 ```php
 $database->save(
     serialize(
-        Hoa\Ruler\Ruler::interprete(
+        Hoa\Ruler\Ruler::interpret(
             'logged(user) and group in ["customer", "guest"] and points > 30'
         )
     )
@@ -183,7 +183,7 @@ unserialize this model. To see the PHP code needed to create such a model, we
 can print the model itself (as an example). Thus:
 
 ```php
-echo Hoa\Ruler\Ruler::interprete(
+echo Hoa\Ruler\Ruler::interpret(
     'logged(user) and group in ["customer", "guest"] and points > 30'
 );
 

Test/Unit/Documentation.php

@@ -124,11 +124,11 @@ public function case_new_operators ( ) {
                     ->isFalse();
     }
 
-    public function case_interprete ( ) {
+    public function case_interpret ( ) {
 
         $this
             ->given(
-                $model = LUT::interprete('group in ["customer", "guest"] and points > 30')
+                $model = LUT::interpret('group in ["customer", "guest"] and points > 30')
             )
             ->when($ledom = unserialize(serialize($model)))
             ->then
@@ -165,7 +165,7 @@ public function case_compile ( ) {
 RESULT;
 
         $this
-            ->when($result = LUT::interprete(
+            ->when($result = LUT::interpret(
                 'logged(user) and group in ["customer", "guest"] and points > 30'
             ) . '')
             ->then