diff --git a/website/source/api/operator.html.md b/website/source/api/operator.html.md
index f0655ba6e..7a78ed25a 100644
--- a/website/source/api/operator.html.md
+++ b/website/source/api/operator.html.md
@@ -420,5 +420,5 @@ The table below shows this endpoint's support for
 ```
 
 - `PreemptionConfig` `(PreemptionConfig)` - Options to enable preemption for various schedulers.
- - `SystemSchedulerEnabled`(bool:true) - Specifies whether preemption for system jobs is enabled. Note that
-         if this is set to true, then system jobs can preempt any other jobs.
\ No newline at end of file
+ - `SystemSchedulerEnabled` (`bool`: `true`) - Specifies whether preemption for system jobs is enabled. Note that
+         if this is set to true, then system jobs can preempt any other jobs.
diff --git a/website/source/docs/internals/scheduling/preemption.html.md b/website/source/docs/internals/scheduling/preemption.html.md
index 6602aa8c5..b30ed6670 100644
--- a/website/source/docs/internals/scheduling/preemption.html.md
+++ b/website/source/docs/internals/scheduling/preemption.html.md
@@ -38,7 +38,7 @@ Preemption is enabled by default in Nomad 0.9. Operators can use the [scheduler
 
 Nomad uses the [job priority](/docs/job-specification/job.html#priority) field to determine what running allocations can be preempted.
 In order to prevent a cascade of preemptions due to jobs close in priority being preempted, only allocations from jobs with a priority
-delta of more than 10 from the job needing placement are chosen.
+delta of more than 10 from the job needing placement are eligible for preemption.
 
 For example, consider a node with the following distribution of allocations: