Introduction updates

Author: danielbachhuber

_posts/2016-11-29-version-1.0.0.md

@@ -8,10 +8,14 @@ Woohoo!
 
 Over the course of 5+ years, hundreds of contributors have worked to bring you WP-CLI v1.0.0, which I'm proud to announce today.
 
-This release represents a level of maturity few open source projects achieve. It also marks a transition point, where the WP-CLI project shifts focus to enabling innovation through the WP-CLI package ecosystem. Building new features as standalone packages promotes faster iteration, more creativity, and distributes the maintenance burden more sustainably. As these community packages find success, we'll bring their learnings back into WP-CLI, alongside bug fixes and minor enhancements.
+This release represents a level of maturity few open source projects achieve. It also marks a moment of transition. The WP-CLI project will shift its focus to the WP-CLI package ecosystem, where it will enable innovation by building and encouraging new features as standalone packages. We hope this approach will promote faster iteration and more creativity, and more sustainably distribute the maintenance burden. As these community packages find success, we'll bring their learnings back into WP-CLI, alongside bug fixes and minor enhancements.
 
 Now that the issue backlog is [down to zero](https://twitter.com/danielbachhuber/status/802951083354009600), I'm personally looking forward to getting more ideas cooking for [runcommand](https://runcommand.io/), my own WP-CLI innovation studio.
 
+Headed to Philly this week? I'll be at Post Status Publish and WCUS (only until mid-afternoon Friday). Say hello!
+
+On with the show...
+
 ### Introducing `WP_CLI::runcommand()`
 
 `WP_CLI::runcommand()` ([doc](/docs/internal-api/wp-cli-runcommand/)) is the new best way to run WP-CLI commands from within your WP-CLI command. It's as though `WP_CLI::run_command()` and `WP_CLI::launch_self()` grew up, married, and had the perfect child.