Update annotations.md

Pazus · web-flow · commit 081b71f518e9 · 2017-01-31T08:38:10.000+03:00
diff --git a/docs/userguide/annotations.md b/docs/userguide/annotations.md
@@ -130,6 +130,6 @@ end test_payment_set_off;
 When you execute tests for your application, the framework constructs test suitу for each test package. Then in combines suites into grouping suites by the `%suitepath` annotation value so that the fully qualifier path to the `recognize_by_num` procedure is `USER:payments.test_payment_recognition.test_recognize_by_num`. If any of its expectations fails then the test is marked as failed, but also the `test_payment_recognition` suite, the parent `payments` suite suite and the whole run.
 From the report you understand that some bug appeared in the payments module, the payments recognition submodule is causing the failure as `recognize_by_num` has an error. As the time goes on you can see the most fragile modules of you application and plan refactoring activities.
 
-A `suitepath` is formed by valid sqlnames separated by dots. The depth of the suites path is not limited. The fully qualified path to a test is formed by `<user>:[<suitepath>.]<test package>.<test procedure>`.
+A `%suitepath` is formed by valid sqlnames separated by dots. The depth of the suites path is not limited. The fully qualified path to a test is formed by `<user>:[<suitepath>.]<test package>.<test procedure>`.
 
-You can also use `suitepath` to define the starting going of tests to execute. If you want to run only payments tests of the `FOO` schema then you gen execute `ut_runner.run('foo:payments');` and all suites that have `payments` in their `%suitepath`s will be executed. This way you can filter the execution up to a single test. Only tests/suites which are children of the defined path are executed and all the parents `beforeall`, `beforeeach`, `aftereach`, `afterall` elements. So all the preparation and cleanup is performed as if you execute all the tests of the schema.
+You can also use `%suitepath` to define the starting going of tests to execute. If you want to run only payments tests of the `FOO` schema then you gen execute `ut_runner.run('foo:payments');` and all suites that have `payments` in their `%suitepath`s will be executed. This way you can filter the execution up to a single test. Only tests/suites which are children of the defined path are executed and all the parents `%beforeall`, `%beforeeach`, `%aftereach`, `%afterall` elements. So all the preparation and cleanup is performed as if you execute all the tests of the schema.
