Skip to content

Commit 00e38d6

Browse files
Update how-to-configure.md
1 parent 2a1b401 commit 00e38d6

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

pages/how-to-configure.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,11 +10,11 @@ The tool is 100% compatible with the SAP CI Framework (Code Inspector). That is,
1010
It is also possible to create a CI-Variant and run the selected CHECKS using this variant at any time. This CI-Variant can be also used in SUT (ABAP CHECK REPORT), ATC or even using SAP-Workbench ABAP Editors (e.g.: SE80) or ADT (e.g.: Eclipse) with ATC/CI Integration directly (the CI-Variant will be asked).
1111

1212
In summary, it is possible to use our tool directly in SCI/SCII, via ATC Integration, via API Call, via SUT, via CI-Variant or via Profile(s).
13-
But keep in mind, one has to choose betweeen using CI-Variants or Using Profile(s). Both features cannot be used in paralell in the same system for the same user.
13+
But keep in mind, one has to choose betweeen using CI-Variants (Code Inspector Variants) or Using Profile/s (via Transaction: Y_CODE_PAL_PROFILE, delivered along with the toolkit). Both features cannot be used in paralell in the same system for the same user. For more details on using CI-Variant/s and Profile/s, please check the section: [How to Execute](https://github.com/SAP/code-pal-for-abap/blob/master/pages/how-to-execute.md).
1414

15-
Every CHECK can be configurable independenlty.
15+
Furtheremore, every single CHECK can be configurable independenlty.
1616

17-
Check configuration: You can,
17+
By the Check configuration: You can,
1818

1919
* Define check's validity period;
2020
* Restrict to objects created since a specific date;

0 commit comments

Comments
 (0)