docs(readme): simply hot reload explanation

Author: David Zukowski

README.md

@@ -107,7 +107,7 @@ The project structure presented in this boilerplate is **fractal**, where functi
 
 Hot reloading is enabled by default when the application is running in development mode (`yarn start`). This feature is implemented with webpack's [Hot Module Replacement](https://webpack.github.io/docs/hot-module-replacement.html) capabilities, where code updates can be injected to the application while it's running, no full reload required. Here's how it works:
 
-* For **JavaScript** modules, a code change will trigger the application to re-render from the top of the tree. Global state is preserved, but any local component state is reset. This differs from React Hot Loader, but we've found that performing a full re-render helps avoid subtle bugs caused by RHL patching. It's important to understand that global state (e.g. your redux store) will persist even when the application re-renders from an HMR update, so it's much more useful than a normal live reload which refreshes the entire page.
+* For **JavaScript** modules, a code change will trigger the application to re-render from the top of the tree. **Global state is preserved (i.e. redux), but any local component state is reset**. This differs from React Hot Loader, but we've found that performing a full re-render helps avoid subtle bugs caused by RHL patching.
 
 * For **Sass**, any change will update the styles in realtime, no additional configuration or reload needed.