From f5c95db8008b858270e76b90c823d3c528acbc02 Mon Sep 17 00:00:00 2001
From: ayushrakesh <115995339+ayushrakesh@users.noreply.github.com>
Date: Tue, 31 Oct 2023 00:47:52 +0530
Subject: [PATCH] Update README.md

---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index e4a50cef1..6d7283be2 100644
--- a/README.md
+++ b/README.md
@@ -332,7 +332,7 @@ option to a path relative to the repository root:
 
 ### Update NUR's lock file after updating your repository
 
-By default we only check for repository updates once a day with an automatic
+By default, we only check for repository updates once a day with an automatic
 github action to update our lock file `repos.json.lock`.
 To update NUR faster, you can use our service at https://nur-update.nix-community.org/
 after you have pushed an update to your repository, e.g.:
@@ -344,7 +344,7 @@ curl -XPOST https://nur-update.nix-community.org/update?repo=mic92
 Check out the [github page](https://github.com/nix-community/nur-update#nur-update-endpoint) for further details
 
 ### HELP! Why are my NUR packages not updating?
-With every build triggered via the URL hook all repositories will be evaluated.Only if the evaluation does not contain errors the repository revision for the user is updated. Typical evaluation errors are:
+With every build triggered via the URL hook, all repositories will be evaluated.Only if the evaluation does not contain errors the repository revision for the user is updated. Typical evaluation errors are:
 
 * Using a wrong license attribute in the metadata.
 * Using a builtin fetcher because it will cause access to external URLs during evaluation. Use pkgs.fetch* instead (i.e. instead of `builtins.fetchGit` use `pkgs.fetchgit`)