From e3ae15895c9b4badea8b740a13806c753c218c47 Mon Sep 17 00:00:00 2001 From: Kevin Pham Date: Thu, 9 Jan 2020 19:50:49 +1100 Subject: [PATCH] Update public folder usage docs to clarify globals Added the relevant topic linked directly, instead of saying it's just in the next section. Adjusted the text so it sounds more like a recommendation rather than a requirement. The topic linked is basically explainer to how you'd reference it using the global window object and ways to avoid linter errors. Thus I used 'reference' to give users a hint of what it the linked page would be for. --- docusaurus/docs/using-the-public-folder.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docusaurus/docs/using-the-public-folder.md b/docusaurus/docs/using-the-public-folder.md index 378bdb604c3..0d50cd22ea6 100644 --- a/docusaurus/docs/using-the-public-folder.md +++ b/docusaurus/docs/using-the-public-folder.md @@ -63,4 +63,4 @@ The `public` folder is useful as a workaround for a number of less common cases: - You want to include a small script like [`pace.js`](https://github.hubspot.com/pace/docs/welcome/) outside of the bundled code. - Some library may be incompatible with Webpack and you have no other option but to include it as a `