Apply suggestions from code review

Co-authored-by: Julien Chaumond <[email protected]>
huggingface · Oct 24, 2024 · e55e9bf · e55e9bf
1 parent 1335391
commit e55e9bf
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/hub/datasets-download-stats.md b/docs/hub/datasets-download-stats.md
@@ -1,6 +1,6 @@
 # Datasets Download Stats
 
-## How are downloads counted for datasets ?
+## How are downloads counted for datasets?
 
 Counting the number of downloads for datasets is not a trivial task, as a single dataset repository might contain multiple files, from multiple subsets and splits (e.g. train/validation/test) and sometimes with many files in a single split. To solve this issue and avoid counting one person's download multiple times, we treat all files downloaded by a user (based on their IP address) within a 5-minute window as a single dataset download. This counting happens automatically on our servers when files are downloaded (through GET or HEAD requests), with no need to collect any user information or make additional calls.
 

diff --git a/docs/hub/models-download-stats.md b/docs/hub/models-download-stats.md
@@ -1,6 +1,6 @@
 # Models Download Stats
 
-## How are downloads counted for models ?
+## How are downloads counted for models?
 
 Counting the number of downloads for models is not a trivial task, as a single model repository might contain multiple files, including multiple model weight files (e.g., with sharded models) and different formats depending on the library (GGUF, PyTorch, TensorFlow, etc.). To avoid double counting downloads (e.g., counting a single download of a model as multiple downloads), the Hub uses a set of query files that are employed for download counting. No information is sent from the user, and no additional calls are made for this. The count is done server-side as the Hub serves files for downloads.