diff --git a/website/source/api/deployments.html.md b/website/source/api/deployments.html.md
index e9163bf0b..ed4029968 100644
--- a/website/source/api/deployments.html.md
+++ b/website/source/api/deployments.html.md
@@ -253,7 +253,8 @@ $ curl \
"DeploymentStatus": null,
"CreateIndex": 19,
"ModifyIndex": 22,
- "CreateTime": 1498775380678486300
+ "CreateTime": 1498775380678486300,
+ "ModifyTime": 1498775380678486300
}
]
```
diff --git a/website/source/api/nodes.html.md b/website/source/api/nodes.html.md
index 9732127ee..0d7ff6c78 100644
--- a/website/source/api/nodes.html.md
+++ b/website/source/api/nodes.html.md
@@ -504,7 +504,8 @@ $ curl \
"CreateIndex": 15052,
"ModifyIndex": 15057,
"AllocModifyIndex": 15052,
- "CreateTime": 1502140975600438500
+ "CreateTime": 1502140975600438500,
+ "ModifyTime": 1502140975600438500
},
...
]
diff --git a/website/source/docs/commands/job/status.html.md.erb b/website/source/docs/commands/job/status.html.md.erb
index 316e4b572..5ff67823c 100644
--- a/website/source/docs/commands/job/status.html.md.erb
+++ b/website/source/docs/commands/job/status.html.md.erb
@@ -23,7 +23,7 @@ information will be displayed.
If the ID is omitted, the command lists out all of the existing jobs and a few of
the most useful status fields for each. As of Nomad 0.7.1, alloc status also shows allocation
-modification time in addition to create time. When the -verbose flag is not set, allocation
+modification time in addition to create time. When the `-verbose` flag is not set, allocation
creation and modify times are shown in a shortened relative time format like `5m ago`.
## General Options
diff --git a/website/source/intro/getting-started/jobs.html.md b/website/source/intro/getting-started/jobs.html.md
index 26287586a..c64092bfb 100644
--- a/website/source/intro/getting-started/jobs.html.md
+++ b/website/source/intro/getting-started/jobs.html.md
@@ -79,8 +79,8 @@ Task Group Desired Placed Healthy Unhealthy
cache 1 1 1 0
Allocations
-ID Node ID Task Group Version Desired Status Created At
-883269bf e42d6f19 cache 0 run running 10/31/17 22:58:40 UTC
+ID Node ID Task Group Version Desired Status Created Modified
+8ba85cef 171a583b cache 0 run running 5m ago 5m ago
```
Here we can see that the result of our evaluation was the creation of an
@@ -101,8 +101,9 @@ Client Status = running
Client Description =
Desired Status = run
Desired Description =
-Created At = 10/31/17 22:58:40 UTC
-Deployment ID = b0a84e74
+Created = 5m ago
+Modified = 5m ago
+Deployment ID = fa882a5b
Deployment Health = healthy
Task "redis" is "running"
@@ -326,13 +327,10 @@ Task Group Desired Placed Healthy Unhealthy
cache 3 3 3 0
Allocations
-ID Node ID Task Group Version Desired Status Created At
-7dce5722 e42d6f19 cache 2 stop complete 11/01/17 17:31:16 UTC
-8cfab5f4 e42d6f19 cache 2 stop complete 11/01/17 17:31:02 UTC
-27bd4a41 e42d6f19 cache 2 stop complete 11/01/17 17:30:40 UTC
-3249e320 e42d6f19 cache 1 stop complete 11/01/17 17:28:28 UTC
-453b210f e42d6f19 cache 1 stop complete 11/01/17 17:28:28 UTC
-883269bf e42d6f19 cache 1 stop complete 10/31/17 22:58:40 UTC
+ID Node ID Task Group Version Desired Status Created Modified
+8ace140d 2cfe061e cache 2 stop complete 5m ago 5m ago
+8af5330a 2cfe061e cache 2 stop complete 6m ago 6m ago
+df50c3ae 2cfe061e cache 2 stop complete 6m ago 6m ago
```
If we wanted to start the job again, we could simply `run` it again.