Link to release rather than zip download; fix documentation typo

Author: simonrob

README.md

@@ -23,7 +23,7 @@ For commercial support or feature requests, please also consider [sponsoring thi
 
 
 ## Getting started
-After cloning or [downloading](https://github.com/simonrob/email-oauth2-proxy/archive/refs/heads/main.zip) (and starring :-) this repository, start by editing the file `emailproxy.config` to add configuration details for each email server and account that you want to use with the proxy.
+After cloning or [downloading](https://github.com/simonrob/email-oauth2-proxy/releases/latest) (and starring :-) this repository, start by editing the file `emailproxy.config` to add configuration details for each email server and account that you want to use with the proxy.
 [Guidance and example account configurations](emailproxy.config) are provided for Office 365, Gmail and several other providers, though you will need to insert your own client credentials for each one (see the [documentation below](#oauth-20-client-credentials)).
 You can remove details from the sample configuration file for services you don't use, or add additional ones for any other OAuth 2.0-authenticated IMAP/POP/SMTP servers you would like to use with the proxy.
 

emailproxy.config

@@ -82,7 +82,7 @@ documentation = Accounts are specified using your email address as the section h
 	Once the proxy is correctly configured, after the first successful use of an account its access token details will
 	be cached for future use, encrypted with the IMAP/POP/SMTP password you used in your email client. By default this
 	configuration file is reused for caching (so it must be writable), but you can specify a different location or
-	method using the proxy's`--cache-store` parameter. You do not need to add or edit cached values manually (i.e.,
+	method using the proxy's `--cache-store` parameter. You do not need to add or edit cached values manually (i.e.,
 	`token_salt`, `access_token`, `access_token_expiry`, `refresh_token` and `last_activity`); the proxy handles this.
 
 	The password used in your email client is not used for authentication with the actual email server (this is done via