Git LFS: references to the old billing platform need to be removed from all files (#60440)

Author: sophietheking

content/billing/concepts/product-billing/git-lfs.md

@@ -39,7 +39,6 @@ redirect_from:
   - /billing/using-the-new-billing-platform/about-billing-for-git-large-file-storage
   - /billing/managing-billing-for-your-products/managing-billing-for-git-large-file-storage/about-billing-for-git-large-file-storage
 shortTitle: Git LFS
-product: '{% data reusables.billing.enhanced-billing-platform-product %}'
 contentType: concepts
 category:
   - Understand product costs

content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository.md

@@ -12,11 +12,12 @@ redirect_from:
 category:
   - Store large files with Git LFS
 ---
+
 ## About {% data variables.large_files.product_name_short %} objects in archives
 
 {% data variables.product.github %} creates [source code archives](/repositories/working-with-files/using-files/downloading-source-code-archives) of your repository in the form of ZIP files and tarballs. People can download these archives on the main page of your repository or as release assets. By default, {% data variables.large_files.product_name_short %} objects are not included in these archives, only the pointer files to these objects. To improve the usability of archives for your repository, you can choose to include the {% data variables.large_files.product_name_short %} objects instead. To be included, the {% data variables.large_files.product_name_short %} objects must be covered by tracking rules in a _.gitattributes_ file that has been committed to the repository.
 
-If you choose to include {% data variables.large_files.product_name_short %} objects in archives of your repository, every download of those archives will count towards bandwidth usage for your account. Each account receives {% data variables.large_files.initial_bandwidth_quota %} per month of bandwidth for free, and you can pay for additional usage. See [AUTOTITLE](/billing/concepts/product-billing/git-lfs).
+If you choose to include {% data variables.large_files.product_name_short %} objects in archives of your repository, every download of those archives will count towards bandwidth usage for your account. Each account receives a free monthly allotment of bandwidth depending on your plan, and you can pay for additional usage. See [AUTOTITLE](/billing/concepts/product-billing/git-lfs).
 
 If you use an external LFS server (configured in your _.lfsconfig_), those LFS files will not be included in archives of the repository. The archive will only contain files that have been committed to {% data variables.product.github %}.
 

content/repositories/releasing-projects-on-github/about-releases.md

@@ -30,7 +30,7 @@ You can manually create release notes while managing a release. Alternatively, y
 
 When viewing the details for a release, the creation date for each release asset is shown next to the release asset.
 
-GitHub will automatically include links to download a zip file and a tarball containing the contents of the repository at the point of the tag's creation.
+{% data variables.product.github %} will automatically include links to download a zip file and a tarball containing the contents of the repository at the point of the tag's creation.
 
 {% ifversion fpt or ghec %}
 People with admin permissions to a repository can choose whether {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in the ZIP files and tarballs that {% data variables.product.github %} creates for each release. For more information, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository).

content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md

@@ -116,6 +116,6 @@ If you need to distribute large files within your repository, you can create rel
 
 {% ifversion fpt or ghec %}
 
-We don't limit the total size of the binary files in the release or the bandwidth used to deliver them. However, each individual file must be smaller than {% data variables.large_files.max_lfs_size %}.
+We don't limit the total size of the binary files in the release or the bandwidth used to deliver them. However, each individual file must be smaller than the maximum file size limit for {% data variables.large_files.product_name_short %} on your plan. See [AUTOTITLE](/repositories/working-with-files/managing-large-files/about-git-large-file-storage).
 
 {% endif %}

data/variables/large_files.yml

@@ -10,12 +10,6 @@ included_storage_free_pro: '10 GiB'
 included_bandwidth_team_enterprise: '250 GiB'
 included_storage_team_enterprise: '250 GiB'
 # storage and bandwidth quota for billing that is not Billing vNext
-initial_bandwidth_quota: '1 GiB'
-initial_storage_quota: '1 GiB'
-max_lfs_size: '2 GiB'
 max_file_size: '2 GiB'
 command_name: lfs
 version_name: https://git-lfs.github.com/spec/v1
-pack_monthly_price: $5 per month
-pack_monthly_bandwidth: '50 GiB'
-pack_monthly_storage: '50 GiB'