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):