Remove Firefox branding from app name in documentation and other files

Dockerfile

@@ -1,7 +1,7 @@
 ##
-# Firefox Send - Mozilla
+# Send
 #
-# License https://github.com/mozilla/send/blob/master/LICENSE
+# License https://gitlab.com/timvisee/send/blob/master/LICENSE
 ##
 
 

README.md

@@ -1,4 +1,4 @@
-# [![Firefox Send](./assets/icon.svg)](https://send.firefox.com/) Firefox Send
+# [![Send](./assets/icon.svg)](https://send.firefox.com/) Firefox Send
 
 [![CircleCI](https://img.shields.io/circleci/project/github/mozilla/send.svg)](https://circleci.com/gh/mozilla/send)
 
@@ -70,7 +70,7 @@ The server is configured with environment variables. See [server/config.js](serv
 
 ## Localization
 
-Firefox Send localization is managed via [Pontoon](https://pontoon.mozilla.org/projects/test-pilot-firefox-send/), not direct pull requests to the repository. If you want to fix a typo, add a new language, or simply know more about localization, please get in touch with the [existing localization team](https://pontoon.mozilla.org/teams/) for your language or Mozilla’s [l10n-drivers](https://wiki.mozilla.org/L10n:Mozilla_Team#Mozilla_Corporation) for guidance.
+Send localization is managed via [Pontoon](https://pontoon.mozilla.org/projects/test-pilot-firefox-send/), not direct pull requests to the repository. If you want to fix a typo, add a new language, or simply know more about localization, please get in touch with the [existing localization team](https://pontoon.mozilla.org/teams/) for your language or Mozilla’s [l10n-drivers](https://wiki.mozilla.org/L10n:Mozilla_Team#Mozilla_Corporation) for guidance.
 
 see also [docs/localization.md](docs/localization.md)
 

docs/acceptance-mobile.md

@@ -7,7 +7,7 @@
 Adapted from [this spreadsheet](https://airtable.com/shrkcBPOLkvNFOrpp)
 
 - [ ] It should look and feel of an Android App
-- [ ] It should look and feel like the Firefox Send Web Client
+- [ ] It should look and feel like the Send Web Client
 
 ### Main Screen
 - [ ] It should clearly Indicate the name of the product
@@ -59,7 +59,7 @@ Adapted from [this spreadsheet](https://airtable.com/shrkcBPOLkvNFOrpp)
 - [ ] It should allow users to opt into notifications when their link is downloaded
 
 ## Annotations on Mobile Spec
-This document tracks differences between the UX spec for Firefox Send and the intended MVP.
+This document tracks differences between the UX spec for Send and the intended MVP.
 
 [Spec Link](https://mozilla.invisionapp.com/share/GNN6KKOQ5XS)
 

docs/deployment.md

@@ -1,5 +1,5 @@
 ## Requirements
-This document describes how to do a full deployment of Firefox Send on your own Linux server. You will need:
+This document describes how to do a full deployment of Send on your own Linux server. You will need:
 
 * A working (and ideally somewhat recent) installation of NodeJS and NPM
 * GIT
@@ -12,14 +12,14 @@ For Debian/Ubuntu systems this probably just means something like this:
 
 ## Building
 * We assume an already configured virtual-host on your webserver with an existing empty htdocs folder
-* First, remove that htdocs folder - we will replace it with Firefox Send's version now
+* First, remove that htdocs folder - we will replace it with Send's version now
 * git clone https://github.com/mozilla/send.git htdocs
 * Make now sure you are NOT root but rather the user your webserver is serving files under (e.g. "su www-data" or whoever the owner of your htdocs folder is)
 * npm install
 * npm run build
 
 ## Running
-To have a permanently running version of Firefox Send as a background process:
+To have a permanently running version of Send as a background process:
 
 * Create a file "run.sh" with:
 ```
@@ -29,11 +29,11 @@ nohup su www-data -c "npm run prod" 2>/dev/null &
 * chmod +x run.sh
 * ./run.sh
 
-Now the Firefox Send backend should be running on port 1443. You can check with:
+Now the Send backend should be running on port 1443. You can check with:
 * telnet localhost 1443
 
 ## Reverse Proxy
-Of course, we don't want to expose the service on port 1443. Instead we want our normal webserver to forward all requests to Firefox send ("Reverse proxy").
+Of course, we don't want to expose the service on port 1443. Instead we want our normal webserver to forward all requests to Send ("Reverse proxy").
 
 # Apache webserver
 

docs/faq.md

@@ -1,4 +1,4 @@
-## How big of a file can I transfer with Firefox Send?
+## How big of a file can I transfer with Send?
 
 There is a 2.5GB file size limit built in to Send(1GB for non-signed in users), however, in practice you may
 be unable to send files that large.  Send encrypts and decrypts the files in
@@ -17,9 +17,9 @@ Many browsers support this standard and should work fine, but some have not
 implemented it yet (mobile browsers lag behind on this, in
 particular).
 
-## Why does Firefox Send require JavaScript?
+## Why does Send require JavaScript?
 
-Firefox Send uses JavaScript to:
+Send uses JavaScript to:
 
 - Encrypt and decrypt files locally on the client instead of the server.
 - Render the user interface.

test/integration/README.md

@@ -1,4 +1,4 @@
-# Integration Tests for [Firefox Send](https://send.firefox.com/).
+# Integration Tests for [Send](https://send.firefox.com/).
 ## How to run the tests locally
 ### Clone the repository
 

test/integration/download-tests.js

@@ -6,7 +6,7 @@ const path = require('path');
 const DownloadPage = require('./pages/desktop/download_page');
 const HomePage = require('./pages/desktop/home_page');
 
-describe('Firefox Send', function() {
+describe('Send', function() {
   const homePage = new HomePage();
   const downloadDir =
     browser.desiredCapabilities['moz:firefoxOptions']['prefs'][

test/integration/homepage-tests.js

@@ -2,7 +2,7 @@
 const assert = require('assert');
 const HomePage = require('./pages/desktop/home_page');
 
-describe('Firefox Send homepage', function() {
+describe('Send homepage', function() {
   this.retries(2);
   const homePage = new HomePage();
   const baseUrl = browser.options['baseUrl'];
@@ -16,7 +16,7 @@ describe('Firefox Send homepage', function() {
   });
 
   it('should have the right title', function() {
-    assert.equal(browser.getTitle(), 'Firefox Send');
+    assert.equal(browser.getTitle(), 'Send');
   });
 
   footerLinks.forEach((link, i) => {

test/integration/progress-tests.js

@@ -2,7 +2,7 @@
 const assert = require('assert');
 const HomePage = require('./pages/desktop/home_page');
 
-describe('Firefox Send progress page', function() {
+describe('Send progress page', function() {
   const homePage = new HomePage();
   beforeEach(function() {
     homePage.open();