From 05c8619f480c47343df66d1b1980fef83820e552 Mon Sep 17 00:00:00 2001
From: Joe Mooring <joe.mooring@veriphor.com>
Date: Tue, 16 Mar 2021 07:16:30 -0700
Subject: [PATCH] Fix sample data for sort function (#1363)

---
 content/en/functions/sort.md        |  3 +--
 content/en/getting-started/usage.md | 12 ++++++------
 2 files changed, 7 insertions(+), 8 deletions(-)

diff --git a/content/en/functions/sort.md b/content/en/functions/sort.md
index b83e6b0bd..9296d04c0 100644
--- a/content/en/functions/sort.md
+++ b/content/en/functions/sort.md
@@ -23,7 +23,7 @@ A sorted array of map values will be returned with the keys eliminated. There ar
 
 ```
 +++
-keywords: [ "tag3", "tag1", "tag2" ]
+tags = [ "tag1", "tag3", "tag2" ]
 +++
 
 // Site config
@@ -62,4 +62,3 @@ Authors: {{ range sort .Site.Params.authors "lastName" "desc" }}{{ .lastName }}
 
 → Outputs Authors: Perkins Linsley Bergevin
 ```
-
diff --git a/content/en/getting-started/usage.md b/content/en/getting-started/usage.md
index e35126fd0..0609acf12 100644
--- a/content/en/getting-started/usage.md
+++ b/content/en/getting-started/usage.md
@@ -120,15 +120,15 @@ in 90 ms
 
 Hugo allows you to set `draft`, `publishdate`, and even `expirydate` in your content's [front matter][]. By default, Hugo will not publish:
 
-1. Content with a future `publishdate` value
-2. Content with `draft: true` status
-3. Content with a past `expirydate` value
+1. Content with `draft: true` status
+2. Content with a past `expirydate` value
+3. Content with a future `publishdate` value
 
 All three of these can be overridden during both local development *and* deployment by adding the following flags to `hugo` and `hugo server`, respectively, or by changing the boolean values assigned to the fields of the same name (without `--`) in your [configuration][config]:
 
-1. `--buildFuture`
-2. `--buildDrafts`
-3. `--buildExpired`
+`-D` or `--buildDrafts`\
+`-E` or `--buildExpired`\
+`-F` or `--buildFuture`\
 
 ## LiveReload