source: fix chevron parsing (#712)

Signed-off-by: Patrick Stephens <[email protected]>

Author: Pat

installation/sources/download-source-code.md

@@ -4,20 +4,20 @@
 
 For production systems, we strongly suggest that you always get the latest stable release of the source code in either zip or tarball format from Github using the following link pattern:
 
-https://github.com/fluent/fluent-bit/archive/refs/tags/v<release version&gt.tar.gz
-https://github.com/fluent/fluent-bit/archive/refs/tags/v<release version&gt.zip
+https://github.com/fluent/fluent-bit/archive/refs/tags/v<release version>.tar.gz
+https://github.com/fluent/fluent-bit/archive/refs/tags/v<release version>.zip
 
-For example for version 1.8.11 the link is the following: [https://github.com/fluent/fluent-bit/archive/refs/tags/v1.8.11.tar.gz](https://github.com/fluent/fluent-bit/archive/refs/tags/v1.8.11.tar.gz)
+For example for version 1.8.12 the link is the following: [https://github.com/fluent/fluent-bit/archive/refs/tags/v1.8.12.tar.gz](https://github.com/fluent/fluent-bit/archive/refs/tags/v1.8.12.tar.gz)
 
 ## Development
 
-For people who aims to contribute to the project testing or extending the code base, can get the development version from our GIT repository:
+For anyone who aims to contribute to the project by testing or extending the code base, you can get the development version from our GIT repository:
 
 ```bash
 $ git clone https://github.com/fluent/fluent-bit
 ```
 
-Note that our _master_ branch is where the development of Fluent Bit happens. Since it's a development version, expect issues when compiling or at run time.
+Note that our _master_ branch is where the development of Fluent Bit happens.
+Since it's a development version, expect issues when compiling or at run time.
 
 We encourage everybody to help us testing every development version, at the end this is what will become stable.
-