From 155cd2e3a251b16e3fe1fa654be0203e57614c76 Mon Sep 17 00:00:00 2001 From: Yingrong Zhao Date: Sat, 23 Mar 2019 19:08:57 -0400 Subject: [PATCH] fix typos (#2235) --- website/content/docs/deploy-preview-links.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/docs/deploy-preview-links.md b/website/content/docs/deploy-preview-links.md index 450c4294..6726965c 100644 --- a/website/content/docs/deploy-preview-links.md +++ b/website/content/docs/deploy-preview-links.md @@ -116,7 +116,7 @@ collections: You may also want preview links for published content as a convenience. You can do this by providing a `site_url` in your configuration, which will be used in place of the deploy preview URL that a backend would provide for an unpublished entry. Just as for deploy preview links to unpublished -content, inks to published content will use any `preview_path` values that are defined in the +content, links to published content will use any `preview_path` values that are defined in the collection configurations. Preview links for published content will also work if you are not using the editorial workflow.