‘Etherpad Lite’ -> ‘Etherpad’

doc/api/http_api.md

@@ -7,7 +7,7 @@ The API gives another web application control of the pads. The basic functions a
 * grant/forbid access to pads
 * get/set pad content
 
-The API is designed in a way, so you can reuse your existing user system with their permissions, and map it to etherpad lite. Means: Your web application still has to do authentication, but you can tell etherpad lite via the api, which visitors should get which permissions. This allows etherpad lite to fit into any web application and extend it with real-time functionality. You can embed the pads via an iframe into your website.
+The API is designed in a way, so you can reuse your existing user system with their permissions, and map it to Etherpad. Means: Your web application still has to do authentication, but you can tell Etherpad via the api, which visitors should get which permissions. This allows Etherpad to fit into any web application and extend it with real-time functionality. You can embed the pads via an iframe into your website.
 
 Take a look at [HTTP API client libraries](https://github.com/ether/etherpad-lite/wiki/HTTP-API-client-libraries) to see if a library in your favorite language.
 
@@ -103,7 +103,7 @@ Responses are valid JSON in the following format:
 
 ### Authentication
 
-Authentication works via a token that is sent with each request as a post parameter.  There is a single token per Etherpad-Lite deployment.  This token will be random string, generated by Etherpad-Lite at the first start. It will be saved in APIKEY.txt in the root folder of Etherpad Lite. Only Etherpad Lite and the requesting application knows this key. Token management will not be exposed through this API. 
+Authentication works via a token that is sent with each request as a post parameter.  There is a single token per Etherpad deployment.  This token will be random string, generated by Etherpad at the first start. It will be saved in APIKEY.txt in the root folder of Etherpad. Only Etherpad and the requesting application knows this key. Token management will not be exposed through this API. 
 
 ### Node Interoperability
 
@@ -132,7 +132,7 @@ creates a new group
 #### createGroupIfNotExistsFor(groupMapper)
  * API >= 1
 
-this functions helps you to map your application group ids to etherpad lite group ids 
+this functions helps you to map your application group ids to Etherpad group ids 
 
 *Example returns:*
   * `{code: 0, message:"ok", data: {groupID: g.s8oes9dhwrvt0zif}}`
@@ -188,7 +188,7 @@ creates a new author
 #### createAuthorIfNotExistsFor(authorMapper [, name])
  * API >= 1
 
-this functions helps you to map your application author ids to etherpad lite author ids 
+this functions helps you to map your application author ids to Etherpad author ids 
 
 *Example returns:*
   * `{code: 0, message:"ok", data: {authorID: "a.s8oes9dhwrvt0zif"}}`

doc/custom_static.md

@@ -1,5 +1,5 @@
 # Custom static files
-Etherpad Lite allows you to include your own static files in the browser, by modifying the files in `static/custom`.
+Etherpad allows you to include your own static files in the browser, by modifying the files in `static/custom`.
 
 * `index.js` Javascript that'll be run in `/`
 * `index.css` Stylesheet affecting `/`

doc/documentation.md

@@ -2,7 +2,7 @@
 
 <!-- type=misc -->
 
-The goal of this documentation is to comprehensively explain Etherpad-Lite,
+The goal of this documentation is to comprehensively explain Etherpad,
 both from a reference as well as a conceptual point of view.
 
 Where appropriate, property types, method arguments, and the arguments

doc/easysync/README.md

@@ -1,2 +1,2 @@
 # About this folder
-We put all documentations we found about the old Etherpad together in this folder. Most of this is still valid for Etherpad Lite
+We put all documentations we found about the original Etherpad together in this folder. Most of this is still valid for the current (node.js based) Etherpad.

doc/localization.md

@@ -1,5 +1,5 @@
 # Localization
-Etherpad lite provides a  multi-language user interface, that's apart from your users' content, so users from different countries can collaborate on a single document, while still having the user interface displayed in their mother tongue.
+Etherpad provides a  multi-language user interface, that's apart from your users' content, so users from different countries can collaborate on a single document, while still having the user interface displayed in their mother tongue.
 
 
 ## Translating
@@ -83,7 +83,7 @@ Everytime the http server is started, it will auto-detect your messages and merg
 
 ### Overwrite core messages
 
-You can overwrite Etherpad Lite's core messages in your plugin's locale files.
+You can overwrite Etherpad's core messages in your plugin's locale files.
 For example, if you want to replace `Chat` with `Notes`, simply add...
 
 *ep_your-plugin/locales/en.json*
@@ -91,4 +91,4 @@ For example, if you want to replace `Chat` with `Notes`, simply add...
 { "ep_your-plugin.h1": "Heading 1"
 , "pad.chat": "Notes"
 }
-```
+```

doc/plugins.md

@@ -1,5 +1,5 @@
 # Plugins
-Etherpad-Lite allows you to extend its functionality with plugins. A plugin registers hooks (functions) for certain events (thus certain features) in Etherpad-lite to execute its own functionality based on these events.
+Etherpad allows you to extend its functionality with plugins. A plugin registers hooks (functions) for certain events (thus certain features) in Etherpad-lite to execute its own functionality based on these events.
 
 Publicly available plugins can be found in the npm registry (see <http://npmjs.org>). Etherpad-lite's naming convention for plugins is to prefix your plugins with `ep_`. So, e.g. it's `ep_flubberworms`. Thus you can install plugins from npm, using `npm install ep_flubberworm` in etherpad-lite's root directory.
 
@@ -104,7 +104,7 @@ Your plugin must also contain a [package definition file](http://npmjs.org/doc/j
 ```
 
 ## Templates
-If your plugin adds or modifies the front end HTML (e.g. adding buttons or changing their functions), you should put the necessary HTML code for such operations in `templates/`, in files of type ".ejs", since Etherpad-Lite uses EJS for HTML templating. See the following link for more information about EJS: <https://github.com/visionmedia/ejs>.
+If your plugin adds or modifies the front end HTML (e.g. adding buttons or changing their functions), you should put the necessary HTML code for such operations in `templates/`, in files of type ".ejs", since Etherpad uses EJS for HTML templating. See the following link for more information about EJS: <https://github.com/visionmedia/ejs>.
 
 ## Writing and running front-end tests for your plugin
 

doc/template.html

@@ -2,12 +2,12 @@
 <html lang="en">
 <head>
   <meta charset="utf-8">
-  <title>__SECTION__ - Etherpad Lite v__VERSION__ Manual &amp; Documentation</title>
+  <title>__SECTION__ - Etherpad v__VERSION__ Manual &amp; Documentation</title>
   <link rel="stylesheet" href="assets/style.css">
 </head>
 <body class="apidoc" id="api-section-__FILENAME__">
   <header id="header">
-    <h1>Etherpad-Lite v__VERSION__ Manual &amp; Documentation</h1>
+    <h1>Etherpad v__VERSION__ Manual &amp; Documentation</h1>
   </header>
 
   <div id="toc">