anchor.diff:  | `spring.batch.job.flatfileitemwriter.saveState`
   | `boolean`
   | `true`
  -| Determines if the state should be saved for restarts.
  +| Determines whether the state should be saved for restarts.
   
   | `spring.batch.job.flatfileitemwriter.shouldDeleteIfEmpty`
   | `boolean`
   | `false`
  -| If set to true, if there is no output (resulting file is empty) it will be deleted when the job completes.
  +| If set to `true`, an empty file (there is no output) is deleted when the job completes.
   
   | `spring.batch.job.flatfileitemwriter.shouldDeleteIfExists`
   | `boolean`
   | `true`
  -| If set to true and a file is found where the output file should be, it will be deleted before the step begins.
  +| If set to `true` and a file is found where the output file should be, it is deleted before the step begins.
   
   | `spring.batch.job.flatfileitemwriter.transactional`
   | `boolean`
   | `FlatFileItemWriter.DEFAULT_TRANSACTIONAL`
  -| Indicates if the reader is a transactional queue (indicating that the items read will be returned to the queue upon a failure).
  -|===
  -
  -To read more about how to configure the `FlatFileItemWriter` you can refer to its documentation https://docs.spring.io/spring-batch/docs/4.3.x/api/org/springframework/batch/item/file/FlatFileItemWriter.html[here].
  +| Indicates whether the reader is a transactional queue (indicating that the items read are returned to the queue upon a failure).
  +|===
  +
  +See the https://docs.spring.io/spring-batch/docs/4.3.x/api/org/springframework/batch/item/file/FlatFileItemWriter.html[`FlatFileItemWriter` documentation].
   
   [[jdbcitemwriter]]
   === JdbcBatchItemWriter
   
   To write the output of a step to a relational database, this starter provides the ability
  -to autoconfigure a `JdbcBatchItemWriter`. The autoconfiguration allows a user to provide their
  -own `ItemPreparedStatementSetter` or `ItemSqlParameterSourceProvider` as well as
  -configuration options via properties specified below.
  +to autoconfigure a `JdbcBatchItemWriter`. The autoconfiguration lets you provide your
  +own `ItemPreparedStatementSetter` or `ItemSqlParameterSourceProvider` and
  +configuration options by setting the following properties:
   
   .`JdbcBatchItemWriter` Properties
   |===
  
positive.code:     <version>2.3.0</version>
  </dependency>
  ----
  
  Gradle:
  [source,groovy]
  ----
  compile "org.springframework.cloud:spring-cloud-starter-single-step-batch-job:2.3.0"
  ----
  
  [[job-definition]]
  == Defining a Job
  
  You can use the starter to define as little as an `ItemReader`, `ItemWriter`, or as much as a full `Job`.
  In this section, we will define what properties are required to be defined to configure a
  `Job`.
  
  [[job-definition-properties]]
  === Properties
  
  To begin, the starter provides a set of properties to be able to configure the basics of a Job with one Step.
  
  .Job Properties
  |===
  
negative.code: | `spring.batch.job.kafkaitemreader.topic`
  | `String`
  | `null`
  | Name of the topic from which to read.
  
  | `spring.batch.job.kafkaitemreader.partitions`
  | `List<Integer>`
  | empty list
  | List of partition indices from which to read.
  
  | `spring.batch.job.kafkaitemreader.pollTimeOutInSeconds`
  | `long`
  