Skip to content

Commit bc3c77b

Browse files
committed
Improve grammar of the doc
1 parent 77f5965 commit bc3c77b

File tree

5 files changed

+11
-11
lines changed

5 files changed

+11
-11
lines changed

docs/gcp/google-app-engine.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Google App Engine
22

3-
You need to setup App Engine before you can deploy to GCP or use GCP resources for local development.
3+
You need to setup an App Engine before you can deploy to GCP or use GCP resources for local development.
44

55
## Environment Variables
66

@@ -14,11 +14,11 @@ You need to setup App Engine before you can deploy to GCP or use GCP resources f
1414
| **Cron Schedule**: |
1515
| `GAE_API_CRON_SCHEDULE_MINS` | The number of minutes between cron intervals. An example value is `1`. |
1616
| **Readiness Check**: |
17-
| `GAE_API_RC_APP_START_TIMEOUT_SEC` | The maximum time, in seconds, an instance has to become ready after the VM and other infrastructure are provisioned. After this period, the deployment fails and is rolled back. You might want to increase this setting if your application requires significant initialization tasks, such as downloading a large file, before it is ready to serve. Must be within range of: `1-3600`. |
18-
| `GAE_API_RC_CHECK_INTERVAL_SEC` | Time interval between checks, in seconds. Must be within range of: `1-300`. |
19-
| `GAE_API_RC_FAILURE_THRESHOLD` | An instance is unhealthy after failing this number of consecutive checks. Must be within range of: `1-10`. |
20-
| `GAE_API_RC_SUCCESS_THRESHOLD` | An unhealthy instance becomes healthy after successfully responding to this number of consecutive checks. Must be within range of: `1-10`. |
21-
| `GAE_API_RC_TIMEOUT_SEC` | Timeout interval for each request, in seconds. Must be within range of: `1-300`. |
17+
| `GAE_API_RC_APP_START_TIMEOUT_SEC` | The maximum time, in seconds, an instance has to become ready after the VM and other infrastructure are provisioned. After this period, the deployment fails and is rolled back. You might want to increase this setting if your application requires significant initialization tasks, such as downloading a large file, before it is ready to serve. Must be within the range of: `1-3600`. |
18+
| `GAE_API_RC_CHECK_INTERVAL_SEC` | Time interval between checks, in seconds. Must be within the range of: `1-300`. |
19+
| `GAE_API_RC_FAILURE_THRESHOLD` | An instance is unhealthy after failing this number of consecutive checks. Must be within the range of: `1-10`. |
20+
| `GAE_API_RC_SUCCESS_THRESHOLD` | An unhealthy instance becomes healthy after successfully responding to this number of consecutive checks. Must be within the range of: `1-10`. |
21+
| `GAE_API_RC_TIMEOUT_SEC` | Timeout interval for each request, in seconds. Must be within the range of: `1-300`. |
2222

2323
## Setup
2424

docs/gcp/google-kubernetes-engine.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ All the goroutines are deployed to a Kubernetes cluster with the same basic step
5555

5656
## Deploy
5757

58-
Once you've got the variables setup it's basically push the image to Google Container Registry (GCR), create the Kubernetes cluster, and then create a Kubernetes deployment. I'll demonstrate with the PHPCS Server. Other than specific `make` commands for each service, these step are all the same.
58+
Once you've got the variables setup it's basically push the image to Google Container Registry (GCR), create the Kubernetes cluster, and then create a Kubernetes deployment. I'll demonstrate it with the PHPCS Server. Other than specific `make` commands for each service, these steps are all the same.
5959

6060
Push the image to GCR:
6161

docs/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ Inspired by the proverb _"A rising tide lifts all boats"_, we want to lift the q
3030

3131
The Tide project is an [official component of the WordPress project](https://make.wordpress.org/tide/) and still in the early stages. Today, Tide scans all WordPress plugins and themes and provides scan results as JSON through the Tide API.
3232

33-
The next step is to start using the JSON output in the WordPress plugin and theme repository to show PHP compatibility information. This will help drive the adoption of the newest PHP versions as both plugin/theme authors and WordPress site owners installing those plugins and theme will be more aware of the PHP compatibility of each plugin/theme.
33+
The next step is to start using the JSON output in the WordPress plugin and theme repository to show PHP compatibility information. This will help drive the adoption of the newest PHP versions as both plugin/theme authors and WordPress site owners installing those plugins and themes will be more aware of the PHP compatibility of each plugin/theme.
3434

3535
Progress can be followed in the WordPress meta issue tracker at https://meta.trac.wordpress.org/ticket/4309.
3636

@@ -119,4 +119,4 @@ Props: [Bartek Makoś (@MakiBM)](https://github.com/MakiBM),
119119

120120
## Contact Us
121121

122-
Have questions? Join us in the [`#tide` channel](https://wordpress.slack.com/messages/C7TK8FBUJ/) in [WordPress Slack](https://make.wordpress.org/chat/). If you're new to Slack, keep it mind that it sometimes takes several hours for community members to respond — thank you for being patient!
122+
Have questions? Join us in the [`#tide` channel](https://wordpress.slack.com/messages/C7TK8FBUJ/) in [WordPress Slack](https://make.wordpress.org/chat/). If you're new to Slack, keep in mind that it sometimes takes several hours for community members to respond — thank you for being patient!

docs/installation/prerequisites.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,4 +21,4 @@ Install [Glide](https://glide.readthedocs.io/en/latest/#installing-glide), a pac
2121

2222
Install [Make for Windows](http://gnuwin32.sourceforge.net/packages/make.htm) _(Windows only)_
2323
- The `make` command is not available on Windows by default and you must install it to be able to use the Tide `make` commands.
24-
- Add `C:\zlib\bin` to your `$PATH` once you've install the package.
24+
- Add `C:\zlib\bin` to your `$PATH` once you've installed the package.

docs/installation/setup.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Setup
22

3-
If you run into any problems getting Tide setup see the [Help](../help.md) page for common issues or ask in the [`#tide` channel](https://wordpress.slack.com/messages/C7TK8FBUJ/) in [WordPress Slack](https://make.wordpress.org/chat/).
3+
If you run into any problems getting Tide setup, then see the [Help](../help.md) page for common issues or ask in the [`#tide` channel](https://wordpress.slack.com/messages/C7TK8FBUJ/) in [WordPress Slack](https://make.wordpress.org/chat/).
44

55
## Environment Variables
66

0 commit comments

Comments
 (0)