just a few Large Files mentions (#2056)

* just a few Large Files mentions

only where it really makes sense imo (it's fine to still mention LFS pointers etc for instance)

* Update docs/hub/storage-limits.md

Co-authored-by: Daniel van Strien <[email protected]>

---------

Co-authored-by: Daniel van Strien <[email protected]>

Author: julien-c

docs/hub/spaces-overview.md

@@ -15,7 +15,7 @@ In the following sections, you'll learn the basics of creating a Space, configur
 <img class="hidden dark:block" src="https://huggingface.co/datasets/huggingface/documentation-images/resolve/main/hub/spaces-blank-space-dark.png"/>
 </div>
 
-Under the hood, Spaces stores your code inside a git repository, just like the model and dataset repositories. Thanks to this, the same tools we use for all the [other repositories on the Hub](./repositories) (`git` and `git-lfs`) also work for Spaces. Follow the same flow as in [Getting Started with Repositories](./repositories-getting-started) to add files to your Space. Each time a new commit is pushed, the Space will automatically rebuild and restart.
+Under the hood, Spaces stores your code inside a git repository, just like the model and dataset repositories. Thanks to this, the same tools we use for all the [other repositories on the Hub](./repositories) (`git` and `git-xet`) also work for Spaces. Follow the same flow as in [Getting Started with Repositories](./repositories-getting-started) to add files to your Space. Each time a new commit is pushed, the Space will automatically rebuild and restart.
 
 For step-by-step tutorials to creating your first Space, see the guides below:
 * [Creating a Gradio Space](./spaces-sdks-gradio)

docs/hub/storage-limits.md

@@ -73,14 +73,14 @@ There are a few reasons for this:
       happen when streaming data and smaller files avoid resuming from the beginning in case of errors.
     - Files are served to the users using CloudFront. From our experience, huge files are not cached by this service
       leading to a slower download speed.
-In all cases no single LFS file will be able to be >50GB. I.e. 50GB is the hard limit for single file size.
+In all cases, no single file will exceed 500GB. I.e. 500GB is the hard limit for a single file size.
 - **Number of commits**: There is no hard limit for the total number of commits on your repo history. However, from
 our experience, the user experience on the Hub starts to degrade after a few thousand commits. We are constantly working to
 improve the service, but one must always remember that a git repository is not meant to work as a database with a lot of
 writes. If your repo's history gets very large, it is always possible to squash all the commits to get a
 fresh start using `huggingface_hub`'s [`super_squash_history`](https://huggingface.co/docs/huggingface_hub/main/en/package_reference/hf_api#huggingface_hub.HfApi.super_squash_history). Be aware that this is a non-revertible operation.
 - **Number of operations per commit**: Once again, there is no hard limit here. When a commit is uploaded on the Hub, each
-git operation (addition or delete) is checked by the server. When a hundred LFS files are committed at once,
+git operation (addition or delete) is checked by the server. When a hundred Large Files are committed at once,
 each file is checked individually to ensure it's been correctly uploaded. When pushing data through HTTP,
 a timeout of 60s is set on the request, meaning that if the process takes more time, an error is raised. However, it can
 happen (in rare cases) that even if the timeout is raised client-side, the process is still
@@ -124,7 +124,7 @@ We recommend that academic and research institutions upgrade to Team, Enterprise
 
 There are several ways to manage and free some storage space in your account or organization. First, if you need more storage space, upgrade to a PRO, Team or Enterprise plan for increased storage limits.
 
-⚠️ **Important**: Deleting LFS files is a destructive operation that cannot be undone. Make sure to backup your files before proceeding.
+⚠️ **Important**: Deleting Large Files is a destructive operation that cannot be undone. Make sure to backup your files before proceeding.
 
 Key points to remember:
 - Deleting only LFS pointers doesn't free up space