diff --git a/packages/documentation-site/patternfly-docs/content/design-guidelines/content/numerics.md b/packages/documentation-site/patternfly-docs/content/design-guidelines/content/numerics.md index 9cee28e742..c694b70ce1 100644 --- a/packages/documentation-site/patternfly-docs/content/design-guidelines/content/numerics.md +++ b/packages/documentation-site/patternfly-docs/content/design-guidelines/content/numerics.md @@ -29,24 +29,24 @@ PatternFly date and time formats follow the American standard. When localizing, Whether you use **absolute** or **relative** timestamps will depend on context. -To represent the exact date and time that an event occurred, use an absolute timestamp, while referencing the examples provided in the [table of date and time formats](#date-and-time-formats). +### Absolute time -To represent how long ago an event occurred, use a relative timestamp. +To represent the exact date and time that an event occurred, use an absolute timestamp. For example, "07 Jan 2020, 23:33 UTC". For more examples, reference the [table of date and time formats.](#date-and-time-formats) -When reporting relative time, align with the following language: +### Relative time + +To represent how long ago an event occurred, use a relative timestamp. When reporting relative time, align with the following language: