Fix some typos, grammar, MyST issues

Author: stevepiercy

docs/i18n-l10n/language-negotiation.md

@@ -60,7 +60,7 @@ For instance, if the site is being presented in a sub-folder (`www.domain.com/en
 
 Another common configuration is to use the browser language request negotiation.
 This means that Plone relies on the `Accept-Language` HTTP header sent by the user's browser.
-The user can configure the list of languages to use in their preferred order, such as in German (de), French (fr), and English (en).
+The user can configure the list of languages to use in their preferred order, such as German (de), French (fr), and English (en).
 In this scenario, Plone will compare its language list with the user's preferences, and will determine in which language to present the site.
 
 The exact working of each of the negotiation options is implemented in the class [`LanguageUtility`](https://github.com/plone/plone.i18n/blob/fc05eb4c131574fd8a4353d5346e17866b3a5e2c/plone/i18n/utility.py#L73) in the module `utility.py` in the package `plone/plone.i18n`.
@@ -69,11 +69,13 @@ Plone also sets a cookie with the language preference of the user.
 This cookie is called `I18N_LANGUAGE`.
 It must be declared as a "technical cookie".
 It is a session cookie, which means that it will be deleted after the user leaves the site.
-To obey the cookie the setting, {guilabel}`Use cookie for manual override` should be set along with {guilabel}`Set the language cookie always`.
+To obey the cookie setting, {guilabel}`Use cookie for manual override` should be set along with {guilabel}`Set the language cookie always`.
 
 Building websites with user interfaces in multiple languages is complicated due to the different expectations of the users and the difficulty of the configuration.
 
-As we will see in the (translating-content-label)= section, Plone will set a special view for the Plone root object called `@@language-switcher` whose implementation lies on `plone.app.multilingual.browser.switcher.LanguageSwitcher`. This language switcher will only rely on the user preferred language to decide where to send the user when she visits the root of the site.
+As we will see in the {doc}`translating-content` chapter, Plone will set a special view for the Plone root object called `@@language-switcher` whose implementation relies on `plone.app.multilingual.browser.switcher.LanguageSwitcher`.
+This language switcher will only rely on the user preferred language to decide where to send the user when they visit the root of the site.
+
 
 (language-negotiation-plone.app.multilingual-is-enabled-label)=
 
@@ -86,7 +88,7 @@ For example, if `en` and `es` are enabled, Plone will create `www.domain.com/en`
 Plone will assume that all the content below `en` is in English, and all content below `es` is in Spanish.
 It will rely on that assumption to present the user interface in those languages when the user is browsing those parts of the site.
 
-As we will see in the {ref}`translating-content-label` chapter, Plone will set a special view for the Plone root object called `@@language-switcher` whose implementation relies on `plone.app.multilngual.browser.switcher.LanguageSwitcher`.
+As we will see in the {doc}`translating-content` chapter, Plone will set a special view for the Plone root object called `@@language-switcher` whose implementation relies on `plone.app.multilingual.browser.switcher.LanguageSwitcher`.
 This language switcher will only rely on the user preferred language to decide where to send the user when they visit the root of the site.
 
 An integrator may want to modify this behavior to always send a user to a given language, or to negotiate the language selection in some other way, such as using the domain, a cookie, or some other techniques.
@@ -100,8 +102,12 @@ As such, there are two options.
 
 ## Changing the default behavior
 
-If for any reason you want to change the default behavior set when using `plone.app.multilingual`, you have 2 options:
+If for any reason you want to change the default behavior set when using `plone.app.multilingual`, you have two options.
 
-1- Override the `language-switcher` view. Plone has a view called `language-switcher` defined in [plone.app.multilingual.browser.switcher.py](https://github.com/plone/plone.app.multilingual/blob/master/src/plone/app/multilingual/browser/switcher.py) which handles the redirection from the root of the Plone site to the proper Language Root Folder. You can override this view using the usual techniques to provide your own implementation.
+1.  Override the `language-switcher` view.
+    Plone has a view called `language-switcher` defined in [plone.app.multilingual.browser.switcher.py](https://github.com/plone/plone.app.multilingual/blob/master/src/plone/app/multilingual/browser/switcher.py) which handles the redirection from the root of the Plone site to the proper Language Root Folder.
+    You can override this view using the usual techniques to provide your own implementation.
 
-2- Create a new view: you can create your own view with your own implementation, configure it properly and then set it as a `default view` for `Plone Site` objects. To do so, you may need to provide your own installation profile with a `Plone Site.xml` file and with the proper configuration.
+1.  Create a new view.
+    You can create your own view with your own implementation, configure it properly, and then set it as a `default view` for `Plone Site` objects.
+    To do so, you may need to provide your own installation profile with a {file}`Plone Site.xml` file and with the proper configuration.