Change some terminology to reflect standard usage:

- "AppEngine" to "App Engine" as per https://cloud.google.com/appengine/docs
- "WebApplication" to "Java web application" or "web application" as per http://docs.oracle.com/javaee/6/tutorial/doc/geysj.html

--
MOS_MIGRATED_REVID=101454871

1 files changed, 9 insertions, 9 deletions

diff --git a/tools/build_rules/appengine/README.md b/tools/build_rules/appengine/README.md
index c9c613f909..9c36468ed4 100644
--- a/tools/build_rules/appengine/README.md
+++ b/tools/build_rules/appengine/README.md
@@ -1,11 +1,11 @@
-# Java AppEngine Rules for Bazel
+# Java App Engine Rules for Bazel
 
 ## Overview
 
 These build rules are used for building
-[Java AppEngine](https://cloud.google.com/appengine/docs/java/)
-application with Bazel. It does not aim at general WebApplication
-support but can be easily modified to handle a standard WebApplication.
+[Java App Engine](https://cloud.google.com/appengine/docs/java/)
+application with Bazel. It does not aim at general Java web application
+support but can be easily modified to handle a standard web application.
 
 * [Setup](#setup)
 * [Basic Example](#basic-example)
@@ -16,14 +16,14 @@ support but can be easily modified to handle a standard WebApplication.
 <a name="setup"></a>
 ## Setup
 
-To be able to use the Java AppEngine rules, you must make the AppEngine SDK
+To be able to use the Java App Engine rules, you must make the App Engine SDK
 available to Bazel. The easiest way to do so is by copying the content of
 `appengine.WORKSPACE` to your workspace file.
 
 <a name="basic-example"></a>
 ## Basic Example
 
-Suppose you have the following directory structure for a simple AppEngine
+Suppose you have the following directory structure for a simple App Engine
 application:
 
 ```
@@ -86,16 +86,16 @@ bind a test server on port 8080. If you wish to select another port,
 simply append the `--port=12345` to the command-line.
 
 Another target `//hello_app:myapp.deploy` allows you to deploy your
-application to AppEngine. It takes an optional argument: the
+application to App Engine. It takes an optional argument: the
 `APP_ID`. If not specified, it uses the default `APP_ID` provided in
-the application. This target needs to be authorized to AppEngine. Since
+the application. This target needs to be authorized to App Engine. Since
 Bazel does not connect the standard input, it is easier to run it by:
 ```
 bazel-bin/hello_app/myapp.deploy APP_ID
 ```
 
 After the first launch, subsequent launch will be registered to
-AppEngine so you can just do a normal `bazel run
+App Engine so you can just do a normal `bazel run
 //hello_app:myapp.deploy APP_ID` to deploy next versions of
 your application.