Minor suggestions post #1245

docs/source/concepts/git_vs_http.mdx

@@ -1,7 +1,7 @@
 # Git vs HTTP paradigm
 
-The `huggingface_hub` library is a library for interacting with the 🤗 Hub, which is a 
-collections of git-based repositories (models, datasets or spaces). There are two main
+The `huggingface_hub` library is a library for interacting with the Hugging Face Hub, which is a 
+collections of git-based repositories (models, datasets or Spaces). There are two main
 ways to access the Hub using `huggingface_hub`.
 
 The first approach, the so-called "git-based" approach, is led by the [`Repository`] class.
@@ -14,32 +14,33 @@ of each approach.
 
 At first, `huggingface_hub` was mostly built around the [`Repository`] class. It provides
 Python wrappers for common `git` commands such as `"git add"`, `"git commit"`, `"git push"`,
-`"git tag"`, `"git checkout"`,...
+`"git tag"`, `"git checkout"`, etc.
+
 The library also helps with setting credentials and tracking large files, which are often
 used in machine learning repositories. Additionally, the library allows you to execute its
 methods in the background, making it useful for uploading data during training.
 
 The main advantage of using a [`Repository`] is that it allows you to maintain a local
-copy of the entire repository on your machine, but this can also be a disadvantage as
+copy of the entire repository on your machine. This can also be a disadvantage as
 it requires you to constantly update and maintain this local copy. This is similar to
 traditional software development where each developer maintains their own local copy and
 pushes changes when working on a feature. However, in the context of machine learning,
 this may not always be necessary as users may only need to download weights for inference
 or convert weights from one format to another without the need to clone the entire
 repository.
 
-## HfApi: a flexible and convenient http client
+## HfApi: a flexible and convenient HTTP client
 
 The [`HfApi`] class was developed to provide an alternative to local git repositories, which
 can be cumbersome to maintain, especially when dealing with large models or datasets. The
 [`HfApi`] class offers the same functionality as git-based approaches, such as downloading
 and pushing files and creating branches and tags, but without the need for a local folder
-to sync.
+that needs to be kept in sync.
 
-In addition to the functionalities already provided by `git` the [`HfApi`] class also offers
+In addition to the functionalities already provided by `git`, the [`HfApi`] class offers
 additional features, such as the ability to manage repos, download files using caching for
 efficient reuse, search the Hub for repos and metadata, access community features such as
-discussions, PRs, and comments, and configure HF Spaces for hardware and secrets.
+discussions, PRs, and comments, and configure Spaces hardware and secrets.
 
 ## What should I use ? And when ?
 
@@ -51,9 +52,9 @@ git-based workflow, pushing regular updates. [`Repository`] is optimized for thi
 situation with its ability to work in the background.
 - If you need to manually edit large files, `git` is the best option as it only sends the
 diff to the server. With the [`HfAPI`] client, the entire file is uploaded with each edit.
-But keep in mind that most large files are binary so do not benefit from git diffs anyway.
+Do keep in mind that most large files are binary so do not benefit from git diffs anyway.
 
 Not all git commands are available through [`HfApi`]. Some may never be implemented, but
 we are always trying to improve and close the gap. If you don't see your use case covered,
 please open [an issue on Github](https://github.com/huggingface/huggingface_hub)! We
-welcome feedback to help build the 🤗 ecosystem with and for our users.
+welcome feedback to help build the 🤗 ecosystem with and for our users.