rename 'Enterprise licenses' to 'Enterprise subscriptions'

content/departments/data-analytics/enablement.md

@@ -35,7 +35,7 @@ Some customers have the contractual right to send us no telemetry at all, or a m
 We also load data to BigQuery from:
 
 - Salesforce: Customer Relationship Management system (CRM)
-- Sourcegraph.com Site-admin pages: customer Enterprise license keys
+- Sourcegraph.com Site-admin pages: customer Enterprise subscriptions and license keys
 - Sourcegraph production database: we query a few particular tables from the production database via terraform to access data for Sourcegraph.com
 - Google Sheets: There are a [number of spreadsheets](https://drive.google.com/drive/folders/1LIfVyhjhh_mpc0SNOFvpNfN2h4CmGQmI) that get loaded into BigQuery
 - Zendesk: customer support ticketing

content/departments/engineering/dev/process/incidents/playbooks/index.md

@@ -17,7 +17,7 @@ In some incidents, we may learn that we need to pause a release.
 
 ## Go-to-market (license and subscription) issues
 
-If a customer is experiencing an issue related to their Enterprise license key status, any member of the Sourcegraph team has authority to generate a new, valid license key for any customer for any number of users that is **valid for up to 7 days** in the [site-admin Enterprise licenses page on Sourcegraph.com](https://sourcegraph.com/site-admin/dotcom/product/subscriptions). This will prevent the initial incident responder from being bottlenecked on a member of the go-to-market team that can validate the customer's Enterprise license status.
+If a customer is experiencing an issue related to their Enterprise license key or Enterprise subscription status, any member of the Sourcegraph team has authority to generate a new, valid license key for any customer for any number of users that is **valid for up to 7 days** in the [site-admin Enterprise subscriptions page on Sourcegraph.com](https://sourcegraph.com/site-admin/dotcom/product/subscriptions). This will prevent the initial incident responder from being bottlenecked on a member of the go-to-market team that can validate the customer's Enterprise subscription status.
 
 The incident responder will need to select a Sourcegraph.com account to attach the subscription to (typically the account should belong to the customer, so they can access the license key directly from their user profile, but in an emergency, the incident responder can use their own account in lieu of asking the customer), and can then manually generate a license key. No license "tags" are necessary.
 

content/departments/engineering/teams/cody/cody-gateway/using.md

@@ -16,7 +16,7 @@ To learn more about Cody Gateway, refer to the [main Cody Gateway page](./index.
 
 Access to the production Cody Gateway instance can be provisioned with the following steps:
 
-1. On sourcegraph.com, go to [**Site admin > Enterprise licenses**](https://sourcegraph.com/site-admin/dotcom/product/subscriptions)
+1. On sourcegraph.com, go to [**Site admin > Enterprise subscriptions**](https://sourcegraph.com/site-admin/dotcom/product/subscriptions)
 2. Find and open a subscription of interest
    1. If you have the license key on hand, you can also use the [license key lookup tool](https://sourcegraph.com/site-admin/dotcom/product/licenses).
 3. Under "Cody services":
@@ -28,11 +28,11 @@ Access to the production Cody Gateway instance can be provisioned with the follo
 
 Once access is provisioned (i.e. enabled via Cody Gateway), the Sourcegraph instance must be [configured](#configuration) as well.
 
-> [!WARNING] Changes in product subscription, such as enabling access and configuring custom rate limits, may take around 2 minutes to propagate.
+> [!WARNING] Changes in Enterprise subscriptions, such as enabling access and configuring custom rate limits, may take around 2 minutes to propagate.
 
 <br />
 
-> [!NOTE] Access to `cody-gateway.sgdev.org` is the same as the above, but requires that the product subscription's associated license have the `dev` or `internal` tag.
+> [!NOTE] Access to `cody-gateway.sgdev.org` is the same as the above, but requires that the Enterprise subscription's associated license have the `dev` or `internal` tag.
 
 ## Configuration
 
@@ -47,9 +47,9 @@ Once access has been provisioned, for self-hosted customers please point them to
 
 ## Analyzing usage
 
-A brief summary of Cody Gateway usage is available in each Enterprise license's "Cody services" section:
+A brief summary of Cody Gateway usage is available in each Enterprise subscriptions's "Cody services" section:
 
-1. On sourcegraph.com, go to [**Site admin > Enterprise licenses**](https://sourcegraph.com/site-admin/dotcom/product/subscriptions)
+1. On sourcegraph.com, go to [**Site admin > Enterprise subscriptions**](https://sourcegraph.com/site-admin/dotcom/product/subscriptions)
 2. Find and open a subscription of interest
    1. If you have the license key on hand, you can also use the [license key lookup tool](https://sourcegraph.com/site-admin/dotcom/product/licenses).
 3. View data in "Cody services" section
@@ -64,7 +64,7 @@ We have quota usage notifications when a customer consumes various percentages o
 
 > [!NOTE] This is most relevant for customers who adopted Cody completions prior to Sourcegraph 5.1.0.
 
-Customers using another provider for completions can be migrated to Cody Gateway by first [provisioning access](#provisioning-access), then configuring `sourcegraph` as the completions provider and replacing `accessToken` with the provisioned product subscription access token.
+Customers using another provider for completions can be migrated to Cody Gateway by first [provisioning access](#provisioning-access), then configuring `sourcegraph` as the completions provider and replacing `accessToken` with the provisioned Enterprise subscription access token.
 
 Models (`completions.chatModel`, `completions.completionModel`, `embeddings.model`, and so on) should be updated such that they are prefixed with the previous provider, either `anthropic/` or `openai/`. For example, `"chatModel": "anthropic/claude-v1"` should be updated to `"chatModel": "anthropic/claude-v1"`.
 

content/departments/technical-success/ce/process/create-new-license.md

@@ -17,11 +17,11 @@ The prospect/customer requires a Sourcegraph.com user account. If an account doe
    - Replace `Company_Name` with the name of the company from Salesforce
    - Separate these components with a hyphen: `-`
    - The `SFDC_Unique_Account_ID` should be taken from the Unique Account ID field on the Account record in Salesforce.
-1. Once the user account is created navigate to the [Enterprise licenses page](https://sourcegraph.com/site-admin/dotcom/product/subscriptions).
-1. Click **Create Enterprise license**.
-   - **Note: You must create a new Enterprise license for each customer instance as well**.
+1. Once the user account is created navigate to the [Enterprise subscriptions page](https://sourcegraph.com/site-admin/dotcom/product/subscriptions).
+1. Click **Create Enterprise subscriptions**.
+   - **Note: You must create a new Enterprise subscriptions for each customer instance as well**.
 1. Search for the user account that was created above in step 3 and click **Create new subscription**.
-1. From the Product Subscription page for that user account, click **Generate new license manually**.
+1. From the Enterprise Subscription page for that user account, click **Generate new license manually**.
 1. Fill out the license details:
    1. The customer name auto-populates from the user account.
    1. Enter the Salesforce Subscription ID if relevant; new trials will not have a subscription ID.

content/departments/technical-success/ce/process/license_keys.md

@@ -21,7 +21,7 @@ This page explains how to create and maintain license keys for prospects and cus
 
 ## Licensing Overview
 
-Sourcegraph requires site administrators to apply a license key to access to various [paid features](https://sourcegraph.com/pricing). License keys are created and managed via the **Site-admin > Enterprise licenses** page on sourcegraph.com/search.
+Sourcegraph requires site administrators to apply a license key to access to various [paid features](https://sourcegraph.com/pricing). License keys are created and managed via the **Site-admin > Enterprise subscriptions** page on sourcegraph.com/search.
 
 ### Accessing Site Admin
 
@@ -34,7 +34,7 @@ License keys can only be generated by site administrators on sourcegraph.com. To
    -- NOTE: If you do not see site-admin permissions, check your profile settings -> Emails section and ensure that your sourcegraph.com email address is added to your profile, verified and it is set as primary. Or you can logout and login using Google Authentication into dotcom, this will create a new account for you with your sourcegraph.com email attached to it.
 
 4. On the top right click on your profile icon and the `site admin` menu will now be available for you to access.
-5. Go to `Enterprise licenses`.
+5. Go to `Enterprise subscriptions`.
 
 ### License Key Mechanics
 
@@ -126,10 +126,10 @@ Note: if a customer needs `multiple production instances` you should create a se
 
 If an existing company or customer needs a new license key for any reason (e.g., they purchase more seats, they upgrade product tiers, or they simply renew), the TA will add a new license key to the _existing_ subscription. In that circumstance, do not click **Create a product subscription**; find the existing subscription on that page and then once viewing it, click **Generate new license manually**.
 
-Visit the **Site-admin > Enterprise licenses** page, find the existing enterprise license key, click into it, and follow the steps below (from the "Click **Generate new license manually**" step onwards).
+Visit the **Site-admin > Enterprise subscriptions** page, find the existing enterprise subscriptions, click into it, and follow the steps below (from the "Click **Generate new license manually**" step onwards).
 
-1. Sign in to sourcegraph.com and visit the **Site-admin > Enterprise licenses** page.
-2. Search for the user associated with the company, and click into the existing Enterprise license ID (left-most column). (You can also check for a user already exists following the instructions in the [Internal Licensing FAQ](#internal-licensing-FAQ) document.)
+1. Sign in to sourcegraph.com and visit the **Site-admin > Enterprise subscriptions** page.
+2. Search for the user associated with the company, and click into the existing Enterprise subscription ID (left-most column). (You can also check for a user already exists following the instructions in the [Internal Licensing FAQ](#internal-licensing-FAQ) document.)
 3. Click **Generate new license manually**. Fill out the license end date (most typically to match the contract terms) and fill in the appropriate license tags. For tags, see [License Key Tags](#license-key-tags) section. Tags must be separated by comma (spaces are ignored).
 4. Set the licensed number of users (note that if you added the `true-up` tag, the company will be able to exceed this count, but administrators will see a warning) and the end date for which the license should be valid, and click **Generate license**.
 5. Finally, copy the license key, and send it to the relevant contact at the company. You can link them to the following docs for instructions on where to add the key: [Updating your license key](https://docs.sourcegraph.com/admin/subscriptions#updating-your-license-key)
@@ -149,7 +149,7 @@ In extreme circumstances, it may be required to revoke a customer's active Sourc
 
 To revoke an active license, follow these steps:
 
-1. Sign in to sourcegraph.com and visit the **Site-admin > Enterprise licenses** page.
+1. Sign in to sourcegraph.com and visit the **Site-admin > Enterprise subscriptions** page.
 2. Navigate to the license that needs to be revoked.
 3. Click on the red **Revoke** button and provide a reason for the revocation.
 

content/departments/technical-success/support/process/engaging-other-teams.md

@@ -237,7 +237,7 @@ And in some cases, the customer resolves the issue or you figure it out on your
 
 ## And sometimes, we need help from teams outside of engineering ...
 
-### Enterprise licenses keys
+### Enterprise subscriptions and licenses
 
 **Keywords**: `subscription`, `license`, `key`, `renew`, `expire`, `contract`