From 3cd43f0f985a3b8a4e74bf5632bd8dac92d751c4 Mon Sep 17 00:00:00 2001 From: Kelly Brazil Date: Mon, 22 Mar 2021 20:57:16 -0700 Subject: [PATCH] formatting --- docs/parsers/upower.md | 2 +- jc/parsers/upower.py | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/parsers/upower.md b/docs/parsers/upower.md index 5af5e2ac..7d6e3687 100644 --- a/docs/parsers/upower.md +++ b/docs/parsers/upower.md @@ -2,7 +2,7 @@ # jc.parsers.upower jc - JSON CLI output utility `upower` command output parser -Calculated epoch time fields are naive (i.e. based on the local time of the system the parser is run on) since there is no unambiguous timezone information in the `upower` command output. +Calculated epoch time field is naive (i.e. based on the local time of the system the parser is run on) since there is no unambiguous timezone information in the `upower` command output. Usage (cli): diff --git a/jc/parsers/upower.py b/jc/parsers/upower.py index 0497a1b9..2d6f4e32 100644 --- a/jc/parsers/upower.py +++ b/jc/parsers/upower.py @@ -1,6 +1,6 @@ """jc - JSON CLI output utility `upower` command output parser -Calculated epoch time fields are naive (i.e. based on the local time of the system the parser is run on) since there is no unambiguous timezone information in the `upower` command output. +Calculated epoch time field is naive (i.e. based on the local time of the system the parser is run on) since there is no unambiguous timezone information in the `upower` command output. Usage (cli):