[Doc] Describe that global styles, scripts can't be inserted when a c…

…omponent is added to a route in Experience Editor

docs/data/routes/docs/fundamentals/application-modes/en.md

@@ -65,6 +65,8 @@ In connected mode, a Sitecore instance is required. The Sitecore databases hold
 
 This mode hosts your JSS app within a Sitecore instance. The application is _server-side rendered (SSR)_ by the Sitecore instance, meaning complete HTML is delivered to the user without any initial JS execution on the client. Integrated mode is always used when editing the site in Sitecore Experience Editor.
 
+> When you add a component using Experience Editor, it will insert only the component HTML generated by SSR into the page, so global styles, scripts can not be updated. For example, some libraries (e.g. [styled-components](https://github.com/styled-components/styled-components)) are inserting global styles using `<style/>` tag after render of new component. After saving and refresing of Experience Editor it will insert all required and updated tags.
+
 > We recommend Headless mode (below) for high traffic production sites. It provides additional scaling options, better scalability, and lower hosting costs for heavy traffic. If using SSR with Connected GraphQL, this is particularly important. Always load test your site with expected traffic before going live.
 
 This mode allows your Sitecore users to manage content, presentation and other marketing features for your JSS app using Sitecore's Experience Editor.