From 2c59262a97933c58051c6aea751cf215e9bb08ef Mon Sep 17 00:00:00 2001
From: Brian Vaughn <brian.david.vaughn@gmail.com>
Date: Thu, 19 Oct 2017 16:57:19 -0700
Subject: [PATCH] Wordsmithing

---
 content/docs/cross-origin-errors.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/content/docs/cross-origin-errors.md b/content/docs/cross-origin-errors.md
index 689bf0cfc..73fa54a43 100644
--- a/content/docs/cross-origin-errors.md
+++ b/content/docs/cross-origin-errors.md
@@ -38,5 +38,4 @@ If you use Webpack, we recommend using the `cheap-module-source-map` setting in
 
 If your application is split into multiple bundles, these bundles may be loaded using JSONP. This may cause errors thrown in the code of these bundles to be treated as cross-origin.
 
-If you use Webpack, you can use the [`crossOriginLoading`](https://webpack.js.org/configuration/output/#output-crossoriginloading) setting in development to add the `crossorigin` attribute to the `<script>` tags generated for the JSONP requests.
-
+To resolve this, use the [`crossOriginLoading`](https://webpack.js.org/configuration/output/#output-crossoriginloading) setting in development to add the `crossorigin` attribute to the `<script>` tags generated for the JSONP requests.