renamed ProcessVariable class in docs to avoid confusion (closes #202)

README.md

@@ -208,11 +208,11 @@ public void handleJobFoo(final JobClient client, final ActivatedJob job, @ZeebeV
 
 ### Using @ZeebeVariablesAsType
 
-When using `autoComplete` (see below) you can also use your own class variables are mapped to (comparable to `getVariablesAsType()` in the API). Therefore use the `@ZeebeVariablesAsType` annotation:
+When using `autoComplete` (see below) you can also use your own class into which the process variables are mapped to (comparable to `getVariablesAsType()` in the API). Therefore use the `@ZeebeVariablesAsType` annotation (`MyProcessVariables` referes to your own class):
 
 ```java
 @ZeebeWorker(type = "foo", autoComplete = true)
-public ProcessVariables handleFoo(@ZeebeVariablesAsType ProcessVariables variables){
+public ProcessVariables handleFoo(@ZeebeVariablesAsType MyProcessVariables variables){
   // do whatever you need to do
   variables.getMyAttribueX();
   variables.setMyAttribueY(42);
@@ -223,7 +223,6 @@ public ProcessVariables handleFoo(@ZeebeVariablesAsType ProcessVariables variabl
 
 
 
-
 ### Completing the job
 
 As a default, your job handler code has to also complete the job, otherwise Zeebe will not know you did your work correctly: