From fe38615456940bde23d72c691df2a55e5868c34c Mon Sep 17 00:00:00 2001 From: Daniel Bachhuber Date: Tue, 10 Oct 2017 04:54:16 -0700 Subject: [PATCH] Fix grammar for original source --- bin/readme/overview-body.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bin/readme/overview-body.md b/bin/readme/overview-body.md index 2ae0b24..7e64788 100644 --- a/bin/readme/overview-body.md +++ b/bin/readme/overview-body.md @@ -1,5 +1,5 @@ `wp profile` monitors key performance indicators of the WordPress execution process to help you quickly identify points of slowness. -Save hours diagnosing slow WordPress sites. Because you can easily run it on any server that supports WP-CLI, `wp profile` compliments Xdebug and New Relic by pointing you in the right direction for further debugging. Because runs on the command line, using `wp profile` means you don't have to install a plugin and deal with the painful dashboard of a slow WordPress site. And, because it's a WP-CLI command, `wp profile` makes it easy to perfom hard tasks (e.g. [profiling a WP REST API response](https://runcommand.io/to/profile-wp-rest-api/)). +Save hours diagnosing slow WordPress sites. Because you can easily run it on any server that supports WP-CLI, `wp profile` compliments Xdebug and New Relic by pointing you in the right direction for further debugging. Because it runs on the command line, using `wp profile` means you don't have to install a plugin and deal with the painful dashboard of a slow WordPress site. And, because it's a WP-CLI command, `wp profile` makes it easy to perfom hard tasks (e.g. [profiling a WP REST API response](https://runcommand.io/to/profile-wp-rest-api/)). [Identify why WordPress is slow in just a few steps](https://runcommand.io/to/identify-wordpress-slowness/) with `wp profile`.