Replace company.com with example.com (#47)

_articles/directory-connector/azure-active-directory.md

@@ -35,7 +35,7 @@ This article will cover how to connect the Bitwarden Directory Connector applica
    {% image directory-connector/azure/new-application.png %}
 4. **Name** your application "Bitwarden"
 5. Set the **Application type** to "Web app / API" 
-6. Set the **Sign-on URL** to any website value, such as "https://company.com". This URL is not used in this setup process so it can be anything.
+6. Set the **Sign-on URL** to any website value, such as "https://example.com". This URL is not used in this setup process so it can be anything.
 7. Click the **Create** button to create the application.
    {% image directory-connector/azure/create-application.png %}
 

_articles/directory-connector/directory-sync.md

@@ -79,7 +79,7 @@ By default the Directory Connector communicates with the Bitwarden public cloud
 1. Run the Directory Connector application.
 2. If you are already logged into the application, go to the **More** tab and **Log Out**.
 3. On the main log in screen, select the **Settings** button.
-4. Enter your installation's base URL and save. For example, `https://bitwarden.company.com`.
+4. Enter your installation's base URL and save. For example, `https://bitwarden.example.com`.
 
 ## Log in to your Bitwarden organization account
 
@@ -220,7 +220,7 @@ The `config` command allow you to specify settings for the Directory Connector C
 
 For example, if you are using a self hosted Bitwarden server you will need to change the endpoint that the Directory Connector CLI communicates with.
 
-    bwdc config server https://bitwarden.company.com
+    bwdc config server https://bitwarden.example.com
 
 You can also use the `config` command to set parameters that require secure storage and cannot be modified directly in the `data.json` database file, such as passwords or access tokens.
 

_articles/directory-connector/ldap-directory.md

@@ -39,7 +39,7 @@ The following directory configuration options can be set:
 
 | Property | Description | Examples |
 |----------|-------------|----------|
-| Server Hostname | The hostname of your directory server. | `ad.company.com` or `ldap.company.local` |
+| Server Hostname | The hostname of your directory server. | `ad.example.com` or `ldap.company.local` |
 | Port | The port on which your directory server is listening. | 389 or 10389 |
 | Root Path | The root path at which the Directory Connector should start all queries. | `cn=users,dc=ad,dc=company,dc=com` |
 | LDAPS | If the server is using LDAP over SSL (LDAPS). |  |
@@ -71,7 +71,7 @@ If you are using Active Directory, many of these settings are predetermined for
 | Revision Date Attribute | The attribute field that specifies when an entry was changed. | whenChanged |
 | Use Email Prefix/Suffix | Email addresses are required by Bitwarden. If your directory users do not have email addresses they will be skipped. Alternatively, you can specify that users without an email address use a prefix attribute concatenated with a suffix to attempt to form a valid email address. |  |
 | Email Prefix Attribute | The attribute field to use when forming a user's email address from the prefix/suffix setting. | accountName |
-| Email Suffix | The specified suffix to use when forming a user's email address from the prefix/suffix setting. | @company.com |
+| Email Suffix | The specified suffix to use when forming a user's email address from the prefix/suffix setting. | @example.com |
 | Sync Users | Sync users to your organization. |  |
 | User Filter | A filter for limiting the users that are synced. Read more at [Configuring user and group sync filters]({% link _articles/directory-connector/user-group-filters.md %}). | (&(givenName=John)) |
 | User Object Class | The name of the class used for the LDAP user object. | user |

_articles/directory-connector/user-group-filters.md

@@ -88,11 +88,11 @@ exclude:Group C,Developers,Some Other Group
 You can include/exclude users directly by using `include` or `exclude` keywords like below:
 
 ```
-include:joe@company.com,bill@company.com,tom@company.com
+include:joe@example.com,bill@example.com,tom@example.com
 ```
 
 ```
-exclude:joe@company.com
+exclude:joe@example.com
 ```
 
 Alternatively, you can filter users based on their Azure AD group membership by using `includeGroup` or `excludeGroup` keywords. You must obtain the Azure AD group ID and include it with the keyword. You can get the group's ID in the [Azure Portal](https://portal.azure.com) or through [Azure AD PowerShell](https://docs.microsoft.com/en-us/powershell/module/azuread/get-azureadgroup?view=azureadps-2.0).
@@ -138,13 +138,13 @@ You can combine both of these filtering options by concatenating the two strings
 Only the include/exclude filter:
 
 ```
-include:joe@company.com,bill@company.com,tom@company.com
+include:joe@example.com,bill@example.com,tom@example.com
 ```
 
 An include/exclude filter + a G Suite `query` search:
 
 ```
-exclude:john@company.com,bill@company.com|orgName=Engineering orgTitle:Manager
+exclude:john@example.com,bill@example.com|orgName=Engineering orgTitle:Manager
 ```
 
 Only the G Suite `query` search (notice the `|` prefix that is required):
@@ -188,13 +188,13 @@ Only the Okta `filter` search (notice the `|` prefix that is required):
 Only the include/exclude filter:
 
 ```
-include:joe@company.com,bill@company.com,tom@company.com
+include:joe@example.com,bill@example.com,tom@example.com
 ```
 
 An include/exclude filter + an Okta `filter`:
 
 ```
-exclude:john@company.com,bill@company.com|profile.firstName eq "John"
+exclude:john@example.com,bill@example.com|profile.firstName eq "John"
 ```
 
 Only the Okta `filter` search (notice the `|` prefix that is required):

_articles/hosting/change-client-environment.md

@@ -13,7 +13,7 @@ By default, client applications such as the browser extensions and mobile apps a
 
 1. If you are currently logged in to your client application, log out.
 2. On the home screen of the client application, select the {% icon fa-cog %} **Settings** icon in the top left corner.
-3. Under the **Self-hosted Environment** section, enter your installation's **Server URL**. For example, if your installation domain was bitwarden.company.com, you would enter https://bitwarden.company.com for the **Server URL**.
+3. Under the **Self-hosted Environment** section, enter your installation's **Server URL**. For example, if your installation domain was bitwarden.example.com, you would enter https://bitwarden.example.com for the **Server URL**.
 4. Save the environment settings and return to the home screen.
 
 You have now configured your client application to point to your self-hosted environment.

_articles/hosting/install-on-premise.md

@@ -67,7 +67,7 @@ If you are looking for a quality provider with affordable prices, we recommend:
 
 By default, Bitwarden will be served through ports 80 (http) and 443 (https) on the localhost machine. You should open these ports so that Bitwarden can be accessed from within and/or outside of the network. You can choose different ports during installation if you like.
 
-If you are serving Bitwarden to the outside world you will need to configure a domain name with DNS records that point to your host machine (ex. bitwarden.company.com). *You should configure this domain before beginning your Bitwarden installation.*
+If you are serving Bitwarden to the outside world you will need to configure a domain name with DNS records that point to your host machine (ex. bitwarden.example.com). *You should configure this domain before beginning your Bitwarden installation.*
 
 Alternatively, if you are only testing you can install Bitwarden to the "localhost" domain.
 
@@ -253,17 +253,17 @@ Manual installations lose the ability to automatically update certain dependenci
 
     Example self-signed certificate:
 
-       # mkdir ./ssl/bitwarden.company.com
+       # mkdir ./ssl/bitwarden.example.com
        openssl req -x509 -newkey rsa:4096 -sha256 -nodes -days 365 \
-         -keyout ./ssl/bitwarden.company.com/private.key \
-         -out ./ssl/bitwarden.company.com/certificate.crt \
+         -keyout ./ssl/bitwarden.example.com/private.key \
+         -out ./ssl/bitwarden.example.com/certificate.crt \
          -reqexts SAN -extensions SAN \
-         -config <(cat /usr/lib/ssl/openssl.cnf <(printf '[SAN]\nsubjectAltName=DNS:bitwarden.company.com\nbasicConstraints=CA:true')) \
-         -subj "/C=US/ST=New York/L=New York/O=Company Name/OU=Bitwarden/CN=bitwarden.company.com"
+         -config <(cat /usr/lib/ssl/openssl.cnf <(printf '[SAN]\nsubjectAltName=DNS:bitwarden.example.com\nbasicConstraints=CA:true')) \
+         -subj "/C=US/ST=New York/L=New York/O=Company Name/OU=Bitwarden/CN=bitwarden.example.com"
 
 7. Update the `server_name`, HTTPS redirects, and `Content-Security-Policy` header with your hostname at `./nginx/default.conf`.
 8.  Generate your own random password strings for the `sqlServer__connectionString` `RANDOM_DATABASE_PASSWORD`, `internalIdentityKey` `RANDOM_IDENTITY_KEY`, and `duo__aKey` `RANDOM_DUO_AKEY` and update the variables at `./env/global.override.env`. Also be sure to apply the same `RANDOM_DATABASE_PASSWORD` at `./env/mssql.override.env`
-9.  Update the `app-id.json` file at `./web/app-id.json` to include your hostname's URL (ex. `https://bitwarden.company.com`).
+9.  Update the `app-id.json` file at `./web/app-id.json` to include your hostname's URL (ex. `https://bitwarden.example.com`).
 10. Configure your SMTP mail server and any other desired application settings at `./env/global.override.env`.
 11. Map the desired user and group id for the Bitwarden containers to run under at `./env/uid.env`.
 

_articles/miscellaneous/cli.md

@@ -335,7 +335,7 @@ The `config` command allow you to specify settings for the CLI to use.
 
 For example, if you are using a self hosted Bitwarden server you will need to change the endpoint that the CLI communicates with.
 
-    bw config server https://bitwarden.company.com
+    bw config server https://bitwarden.example.com
 
 ### Update