[gnome-browser-extension] README: better wording and grammar

[Yuri Konotopov <ykonotopov src gnome org>]

commit 1aeca1cbe5ecf41445974f46be3f0467d1f2c6f3
Author: Mae Dartmann <hello maedartmann name>
Date:   Mon Jul 18 13:58:20 2022 +0200

    README: better wording and grammar
    
    Signed-off-by: Mae Dartmann <hello maedartmann name>
    
     Changes to be committed:
            modified:   README.md

 README.md | 34 +++++++++++++++++-----------------
 1 file changed, 17 insertions(+), 17 deletions(-)
---
diff --git a/README.md b/README.md
index 8327567..c888d07 100644
--- a/README.md
+++ b/README.md
@@ -1,43 +1,43 @@
 # GNOME Shell browser extension
 ## Introduction
 
-This repository contains browser extension that provides integration with GNOME Shell and the corresponding
-extensions repository https://extensions.gnome.org/.
+This repository contains the browser extension that provides integration with GNOME Shell and the 
corresponding
+extensions repository at https://extensions.gnome.org/.
 
-This extension works in conjuction with [os-native 
counterpart](https://gitlab.gnome.org/nE0sIghT/gnome-browser-connector).
+This extension works in conjunction with its [os-native 
counterpart](https://gitlab.gnome.org/nE0sIghT/gnome-browser-connector).
 
 ## Build
 
-First you need to install build requirements:
+First you need to install the build requirements:
 - meson
 - python3
 - gettext
 - p7zip
 - polib python module
 
-Then invoke meson to build extension:
+Then invoke meson to build the extension:
 ```shell
     meson builddir
     cd builddir
     meson compile
 ```
 
-This will produce 2 zip files in `builddir` folder:
+This will produce 2 zip files in the `builddir` folder:
 - extension-chrome.zip
-- extension-firefox
+- extension-firefox.zip
 
-Those files can be uploaded to corresponding browser Addons website.  
-There are also unpacked extensions available under `builddir/extension` folder that can be loaded in web 
browsers for development purposes.
+These files can be uploaded to the corresponding browser add-on websites.  
+Unpacked extensions are also available in the `builddir/extension` folder which can be loaded in web 
browsers for development purposes.
 
 ## Translations
 
-This project uses [GNOME Translation Project](https://wiki.gnome.org/TranslationProject).   Translation 
statistics can be obtained on corresponding Damned Lies page.
+This project uses the [GNOME Translation Project](https://wiki.gnome.org/TranslationProject).   Translation 
statistics can be obtained on the corresponding Damned Lies page.
 
 ### Translation strings handling
 
-All user-visible web extension strings are maintained by developers in messages.json file at 
`extension/extension/_locale/en/` folder. File format is described 
[here](https://developer.chrome.com/extensions/i18n-messages).
+All user-visible web extension strings are maintained by developers in the messages.json file, which is 
located in the `extension/extension/_locale/en/` folder. The file format is described 
[here](https://developer.chrome.com/extensions/i18n-messages).
 
-Gettext template located in `po/chrome-gnome-shell.pot` and auto generated using meson:
+The Gettext template is located in `po/chrome-gnome-shell.pot` and automatically generated using meson:
 
 ```shell
     meson -Dbuild_messages=true -Dbuild_extension=false builddir
@@ -46,13 +46,13 @@ Gettext template located in `po/chrome-gnome-shell.pot` and auto generated using
 ```
 
 As result of those commands:
-1. New gettext template will be saved to `po/chrome-gnome-shell.pot` file.
-2. All `po/*.po` files will be updated by `msgmerge` using new gettext template.
-3. All extension locales (messages.json) will be generated from gettext po files.
+1. The new gettext template will be saved in `po/chrome-gnome-shell.pot`.
+2. All `po/*.po` files will be updated by `msgmerge` using the new gettext template.
+3. All extension locales (messages.json) will be generated from the gettext po files.
 
 This process is fully compatible with Damned Lies.
 
-There is limited number of [supported 
locales](https://developer.chrome.com/webstore/i18n?csw=1#localeTable).  
+There is a limited number of [supported 
locales](https://developer.chrome.com/webstore/i18n?csw=1#localeTable).  
 If you use an unsupported locale, Google Chrome will ignore it.
 
-To create a new translation you can use msginit command (or any po editor) and gettext template. Please 
refer [Translation Project wiki page](https://wiki.gnome.org/TranslationProject) for further info about 
optimal translation workflow.
+To create a new translation, you can use the `msginit` command (or any po editor) and the gettext template. 
Please refer to the [Translation Project wiki page](https://wiki.gnome.org/TranslationProject) for further 
information about optimal translation workflow.