improve modifier workaround description

readme/usage.md

@@ -50,25 +50,21 @@ For example a combination of `LEFTSHIFT + a` for `b` would write "B" insetad,
 because shift will be activated before you hit the "a". Therefore the
 environment will see shift and a "b", which will then be capitalized.
 
-A better option for a key combination would be `KP1 + a` instead of 
-`LEFTSHIFT + a`, because there won't be any side effect. You can disable
-`KP1` by mapping it to `disable`, so you won't trigger writing a "1" into
-your focused application.
+The first option to work around this issue is to use `KP1 + a` instead of 
+`LEFTSHIFT + a`. You can disable `KP1` by mapping it to `disable`, so you
+won't trigger writing a "1" into your focused application.
 
 <p align="center">
   <img src="combination.png"/>
 </p>
 
-But you can also work around it by releasing the modifier in your
-combination. This is a bit weird to use right now and there is probably
-room for improvement:
+The second option is to release the modifier in your combination by writing
+the modifier one more time. This will write lowercase "a" characters.
 
 <p align="center">
   <img src="combination_workaround.png"/>
 </p>
 
-This will write lowercase "a" characters.
-
 ## Writing Combinations
 
 You can write `Control_L + a` as mapping, which will inject those two