Change the unit for size limit for GEI (#57668)

Author: pnsk

content/migrations/using-github-enterprise-importer/migrating-between-github-products/about-migrations-between-github-products.md

@@ -61,8 +61,8 @@ Different size limits per repository apply to the compressed archive, depending
 
 Limit | GHES <3.8.0 | GHES 3.8.x-3.11.x | GHES 3.12.x | GHES 3.13.0+
 ----- | ----------- | ----------------- | ----------- | ------------
-Git source | 2GB | 10GB | 20GB | 40GB (public preview)
-Metadata | 2GB | 10GB | 20GB | 40GB (public preview)
+Git source | 2GiB | 10GiB | 20GiB | 40GiB (public preview)
+Metadata | 2GiB | 10GiB | 20GiB | 40GiB (public preview)
 
 ### Data that is not migrated
 
@@ -122,7 +122,7 @@ When you migrate a repository, either directly or as part of an organization mig
     * Allow merge commits (commit message setting is reset to the default message)
     * Allow squash merging (commit message setting is reset to the default message)
     * Allow rebase merging
-* Releases (up to 10 GB per repository)
+* Releases (up to 10 GiB per repository)
 * User history for the above data
 * Attachments (see [AUTOTITLE](/get-started/writing-on-github/working-with-advanced-formatting/attaching-files))
 
@@ -147,7 +147,7 @@ When you migrate a repository directly, teams and team access to repositories ar
 ### Limitations of {% data variables.product.prodname_importer_proper_name %}
 
 * {% data reusables.enterprise-migration-tool.git-repo-size-limit %}
-* **40 GB limit for metadata ({% data variables.release-phases.public_preview %}):** The {% data variables.product.prodname_importer_secondary_name %} cannot migrate repositories with more than 40 GB of metadata. Metadata includes issues, pull requests, releases, and attachments. In most cases, large metadata is caused by binary assets attached to releases. You can exclude releases from the migration with the `migrate-repo` command's `--skip-releases` flag, and then move your releases manually after the migration.
+* **40 GiB limit for metadata ({% data variables.release-phases.public_preview %}):** The {% data variables.product.prodname_importer_secondary_name %} cannot migrate repositories with more than 40 GiB of metadata. Metadata includes issues, pull requests, releases, and attachments. In most cases, large metadata is caused by binary assets attached to releases. You can exclude releases from the migration with the `migrate-repo` command's `--skip-releases` flag, and then move your releases manually after the migration.
 {% data reusables.enterprise-migration-tool.limitations-of-migration-tooling %}
 
 ## Getting started

data/reusables/enterprise-migration-tool/git-repo-size-limit.md

@@ -1 +1 @@
-**40 GB size limit for a Git repository ({% data variables.release-phases.public_preview %}):** This limit applies only to the source code. To check if the repository archive is over the limit, use the [git-sizer](https://github.com/github/git-sizer) tool and review the total blob size in the output. The git-sizer tool also helps to identify potential issues related to large files, blob size, commit size, and tree counts that could impact migrations.
+**40 GiB size limit for a Git repository ({% data variables.release-phases.public_preview %}):** This limit applies only to the source code. To check if the repository archive is over the limit, use the [git-sizer](https://github.com/github/git-sizer) tool and review the total blob size in the output. The git-sizer tool also helps to identify potential issues related to large files, blob size, commit size, and tree counts that could impact migrations.

data/reusables/enterprise-migration-tool/limitations-of-migration-tooling.md

@@ -1,4 +1,4 @@
-* **400 MB file size limit:** When migrating a repository with {% data variables.product.prodname_importer_proper_name %}, no single file in your Git repository can be larger than 400 MB. Consider using {% data variables.large_files.product_name_short %} for storing large files. For more information, see [AUTOTITLE](/repositories/working-with-files/managing-large-files).
+* **400 MiB file size limit:** When migrating a repository with {% data variables.product.prodname_importer_proper_name %}, no single file in your Git repository can be larger than 400 MiB. Consider using {% data variables.large_files.product_name_short %} for storing large files. For more information, see [AUTOTITLE](/repositories/working-with-files/managing-large-files).
 * **{% data variables.large_files.product_name_short %} objects not migrated:** The {% data variables.product.prodname_importer_secondary_name %} can migrate repositories that use {% data variables.large_files.product_name_short %}, but the LFS objects themselves will not be migrated. They can be pushed to your migration destination as a follow-up task after the migration is complete. For more information, see [AUTOTITLE](/repositories/creating-and-managing-repositories/duplicating-a-repository#mirroring-a-repository-that-contains-git-large-file-storage-objects).
 * **Follow-up tasks required:** When migrating between {% data variables.product.prodname_dotcom %} products, certain settings are not migrated and must be reconfigured in the new repository. For a list of follow-up tasks you'll need to complete after each migration, see [AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-between-github-products/overview-of-a-migration-between-github-products#completing-follow-up-tasks).
 * **Delayed code search functionality:** Re-indexing the search index can take a few hours after a repository is migrated, and code searches may return unexpected results until re-indexing is complete.