improve readibility + shorten link

Author: viankakrisna

Diff for: packages/react-dev-utils/README.md

@@ -220,10 +220,10 @@ compiler.plugin('done', function(stats) {
 });
 ```
 
-#### `printBuildError(error: Object): String`
+#### `printBuildError(error: Object): void`
 
 Prettify some known build errors.
-Pass an Error object to log a prettified error message in the console
+Pass an Error object to log a prettified error message in the console.
 
 ```
   const printBuildError = require('react-dev-utils/printBuildError')

Diff for: packages/react-dev-utils/printBuildError.js

@@ -42,11 +42,9 @@ module.exports = function printBuildError(err) {
     } catch (ignored) {
       console.log('Failed to minify the code.', err);
     }
-    console.log('Read more here:');
-    console.log(
-      'https://github.com/facebookincubator/create-react-app/blob/master/packages/react-scripts/template/README.md#npm-run-build-fails-to-minify\n'
-    );
+    console.log('Read more here: http://bit.ly/2tRViJ9');
   } else {
     console.log((message || err) + '\n');
   }
+  console.log();
 };

Diff for: packages/react-scripts/template/README.md

@@ -2001,13 +2001,13 @@ This will only work for locales that have been explicitly imported before.
 
 ### `npm run build` fails to minify
 
-Some dependencies may be shipping their source which our minify can't process.
-Because running Babel on `node_modules` is slow, we cannot compile it to es5 
-before minifying it. Possible solutions are:
-1. Raise an issue with the library author to ship compiled es5.
-2. If it's small and compatible with out babel preset, you can place the
-source in ./src.
-3. Fork the project repo and publish an es5 version of it.
+You may occasionally find a package you depend on needs compiled or ships code for a non-browser environment.<br>
+This is considered poor practice in the ecosystem and does not have an escape hatch in Create React App.<br>
+<br>
+To resolve this:
+1. Open an issue on the dependency's issue tracker and ask that the package be published pre-compiled (retaining ES6 Modules).
+2. Fork the package and publish a corrected version yourself.
+3. If the dependency is small enough, copy it to your `src/` folder and treat it as application code.
 
 ## Something Missing?