Addressed some grammar suggestions

Signed-off-by: Albert Callarisa <[email protected]>

Author: acroca

daprdocs/content/en/reference/api/jobs_api.md

@@ -38,7 +38,7 @@ Parameter | Description
 `repeats` | An optional number of times in which the job should be triggered. If not set, the job runs indefinitely or until expiration.
 `ttl` | An optional time to live or expiration of the job. Accepts a "point in time" string in the format of RFC3339, Go duration string (calculated from job creation time), or non-repeating ISO8601.
 `overwrite` | A boolean value to specify if the job can overwrite an existing one with the same name. Default value is `false`
-`failure_policy` | An optional failure policy for the job. Details of the format are below. If not set, the job will be retried up to 3 times with a delay of 1 second between retries.
+`failure_policy` | An optional failure policy for the job. Details of the format are below. If not set, the job is retried up to 3 times with a delay of 1 second between retries.
 
 #### schedule
 `schedule` accepts both systemd timer-style cron expressions, as well as human readable '@' prefixed period strings, as defined below.
@@ -69,10 +69,10 @@ Entry                  | Description                                | Equivalent
 `failure_policy` specifies how the job should handle failures.
 
 It can be set to `constant` or `drop`.
-- The `constant` policy will retry the job based on the configuration
-  - `max_retries` configures how many times the job should be retried. Not setting this will make it retry indefinitely.
-  - `interval` configures the delay between retries. Not setting this will make it retry immediately.
-- The `drop` policy will drop the job after the first failure, without retrying.
+- The `constant` policy retries the job based on the configuration.
+  - `max_retries` configures how many times the job should be retried. Not setting this makes it retry indefinitely.
+  - `interval` configures the delay between retries. Not setting this makes it retry immediately.
+- The `drop` policy drops the job after the first failure, without retrying.
 
 ##### Example 1