Update README and CONTRIBUTING

CONTRIBUTING.md

@@ -26,4 +26,4 @@ composer analyze # Analyze code
 composer build   # Build JS/CSS resources, and the final phar file
 ```
 
-Note: Full format and build depends on npm and bundler being in your `$PATH`.
+Note: Full format and build depends on `npm` and `bundler` being in your `$PATH`.

README.md

@@ -6,21 +6,19 @@
 
 ## What am I looking at?
 
-At first glance Kint is just a pretty replacement for **[var_dump()](http://php.net/manual/en/function.var-dump.php)**, **[print_r()](http://php.net/manual/en/function.print-r.php)** and **[debug_backtrace()](http://php.net/manual/en/function.debug-backtrace.php)**.
+At first glance Kint is just a pretty replacement for **[var_dump()](https://secure.php.net/function.var_dump)**, **[print_r()](https://secure.php.net/function.print_r)** and **[debug_backtrace()](https://secure.php.net/function.debug_backtrace)**.
 
-However, it's much, *much* more than that. Even the excellent `xdebug` var_dump improvements don't come close - you will eventually wonder how you developed without it. 
-
-Just to list some of the most useful features:
+However, it's much, *much* more than that. You will eventually wonder how you developed without it.
 
 ## Installation
 
 One of the main goals of Kint is to be **zero setup**.
 
-[Download the file](https://raw.githubusercontent.com/kint-php/kint/master/build/kint.php) and simply
+[Download the file](https://raw.githubusercontent.com/kint-php/kint/master/build/kint.phar) and simply
 ```php
 <?php
 
-require 'kint.php';
+require 'kint.phar';
 ```
 
 ### Or, if you use Composer:
@@ -50,20 +48,27 @@ d('Get off my lawn!'); // Debugs no longer have any effect
 
 ## Tips & Tricks
 
-* Kint is enabled by default, set `Kint::$enabled_mode = false;` to turn its functionality completely off. The best practice is to enable Kint in a development environment only (or for example `Kint::$enabled_mode = ($_SERVER['REMOTE_ADDR'] === '<your IP>');`) - so even if you accidentally leave a dump in production, no one will know.
-* Kint has *keyboard shortcuts*! When Kint is visible, press <kbd>D</kbd> on the keyboard and you will be able to traverse the tree with arrows, <kbd>h</kbd><kbd>j</kbd><kbd>k</kbd><kbd>l</kbd>, and <kbd>tab</kbd> keys - and expand/collapse nodes with <kbd>space</kbd> or <kbd>enter</kbd>.
-* Clicking the <kbd>+</kbd> sign or the bar will open/close it.
+* Kint is enabled by default, set `Kint::$enabled_mode = false;` to turn it completely off.  
+  The best practice is to enable Kint in a development environment only - so even if you accidentally leave a dump in production, no one will know.
+* See the buttons on the right of the output? Click them to open a new tab, show the access path for the value, or show a search box.
+* There are a couple of real-time modifiers you can use:
+    * `~d($var)` this call will output in plain text format.
+    * `+d($var)` will disregard depth level limits and output everything.  
+      *Careful, this can hang your browser on large objects!*
+    * `!d($var)` will expand the output automatically.
+    * `-d($var)` will attempt to `ob_clean` the previous output.
+    * You can combine modifiers too: `~+d($var)`
 * Double clicking the <kbd>+</kbd> sign will open/close it and all its children.
 * Triple clicking the <kbd>+</kbd> sign in will open/close everything on the page.
-* See the tiny arrows on the right of the output? Click them to open the node in a separate tab, or to show the access path for the value.
-* There are a couple of real-time modifiers you can use:
-  * `~d($var)` this call will output in plain text format.
-  * `+d($var)` will disregard depth level limits and output everything. (Careful, this can hang your browser on large objects!)
-  * `!d($var)` will expand the output automatically.
-  * `-d($var)` will attempt to `ob_clean` the previous output.
-  * You can combine modifiers too: `~+d($var)`
-* To change display theme, use `Kint_Renderer_Rich::$theme = '<theme name>';` where available options are: `'original.css'` (default), `'solarized.css'`, `'solarized-dark.css'` and `'aante-light.css'`. You can also pass the absolute path to a CSS file to use that instead.
-* `dd()`, `sd()`, and `ddd()` were removed in Kint 2, but you can make them yourself with [helper aliases](https://kint-php.github.io/kint/advanced/#helperfuncs)
+* Add heavy classes to the blacklist to improve performance:  
+  `Kint\Parser\BlacklistPlugin::$shallow_blacklist[] = 'Psr\Container\ContainerInterface';`
+* To change display theme, use `Kint\Renderer\RichRenderer::$theme = 'theme.css';`. You can pass the absolute path to a CSS file, or use one of the built in themes:
+    * `original.css` (default)
+    * `solarized.css`
+    * `solarized-dark.css`
+    * `aante-light.css`
+* Kint has *keyboard shortcuts*! When Kint is visible, press <kbd>D</kbd> on the keyboard and you will be able to traverse the tree with arrows, <kbd>H</kbd><kbd>J</kbd><kbd>K</kbd><kbd>L</kbd>, and <kbd>TAB</kbd> keys - and expand/collapse nodes with <kbd>SPACE</kbd> or <kbd>ENTER</kbd>.
+* You can write plugins and wrapper functions to customize dump behavior!
 * Read [the full documentation](https://kint-php.github.io/kint/) for more information
 
 ## Authors