Fixed Javadoc

Author: chrisgleissner

README.md

@@ -231,7 +231,7 @@ Properties can be overridden when starting a job via REST. You can then access t
 
 ### @Value
 
-Annotate your Spring bean method with `@StepScope` and use the `@Value("#{jobParameters['name']}")` annotation on a method parameter 
+Annotate your Spring bean method with `@StepScope` and use the `@Value` annotation on a method parameter 
 to specify the desired job parameter name. 
 
 Please note that this approach won't transparently fall back to Spring environment properties. Thus,
@@ -240,7 +240,7 @@ if this is desired, you should manually check if a job parameter is `null` and i
 Example:
 ```java
 @Bean @StepScope  
-ItemWriter<Object> writer(@Value("#{jobParameters['propName']}") String prop) {
+ItemWriter<Object> writer(@Value("#{jobParameters['sampleProperty']}") String sampleProperty) {
     // ... 
 }
 ```
@@ -255,9 +255,10 @@ Example:
 ```java
 Job job = jobBuilder.createJob("sampleJob", propertyResolver -> {
     String propertyValue = propertyResolver.getProperty("sampleProperty");
-    ...
+    // ...
 });
 ```
+
 ### JobProperties
 
 In case you don't execute the same job concurrently, you may also look up properties from the `JobProperties` singleton. 
@@ -275,7 +276,7 @@ ItemWriter<Object> writer() {
     return new ItemWriter<Object>() {
         @Override
         public void write(List<?> items) throws Exception {
-           String prop = JobPropertyResolvers.JobProperties.of("sampleJob").getProperty("sampleProperty");
+           String sampleProperty = JobPropertyResolvers.JobProperties.of("sampleJob").getProperty("sampleProperty");
            // ...
         }
     }

util/src/main/java/com/github/chrisgleissner/springbatchrest/util/core/property/JobPropertyResolvers.java

@@ -22,18 +22,20 @@ public class JobPropertyResolvers implements Consumer<JobExecution> {
 
     /**
      * @deprecated Accessing {@link org.springframework.batch.core.Job} properties via this singleton is not safe for
-     * asynchronously executing the same code>Job</code> multiple times with different properties. In this case a {@link JobExecution}
+     * asynchronously executing the same <code>Job</code> multiple times with different properties. In this case a {@link JobExecution}
      * may incorrectly use the properties of another, concurrently running <code>JobExecution</code> of the same <code>Job</code>.
      *
      * <p>
      * Instead, it is recommended to access job properties via either {@link StepExecution#getJobParameters()} or by annotating your
      * Spring-wired job beans with <code>@Value("#{jobParameters['key']}")</code>. You can get a handle of a <code>StepExecution</code>
      * by implementing {@link org.springframework.batch.core.StepExecutionListener} or extending
      * {@link com.github.chrisgleissner.springbatchrest.util.core.tasklet.StepExecutionListenerTasklet}.
+     * </p>
      *
      * <p>For convenience, when using
      * {@link com.github.chrisgleissner.springbatchrest.util.core.JobBuilder#createJob(String, Consumer)} to build a job,
      * the returned {@link PropertyResolver} will first resolve against job properties, then against Spring properties.
+     * </p>
      *
      * @see com.github.chrisgleissner.springbatchrest.util.core.JobBuilder#createJob(String, Consumer)
      */