docs: Fix typos

doc_src/cmds/fish_git_prompt.rst

@@ -27,7 +27,7 @@ The ``fish_git_prompt`` function displays information about the current git repo
 There are numerous customization options, which can be controlled with git options or fish variables. git options, where available, take precedence over the fish variable with the same function. git options can be set on a per-repository or global basis. git options can be set with the ``git config`` command, while fish variables can be set as usual with the :ref:`set <cmd-set>` command.
 
 - ``$__fish_git_prompt_show_informative_status`` or the git option ``bash.showInformativeStatus`` can be set to enable the "informative" display, which will show a large amount of information - the number of dirty files, unpushed/unpulled commits, and more.
-  In large repositories, this can take a lot of time, so it you may wish to disable it in these repositories with  ``git config --local bash.showInformativeStatus false``. It also changes the characters the prompt uses to less plain ones (``✚`` instead of ``*`` for the dirty state for example) , and if you are only interested in that, set ``$__fish_git_prompt_use_informative_chars`` instead.
+  In large repositories, this can take a lot of time, so you may wish to disable it in these repositories with  ``git config --local bash.showInformativeStatus false``. It also changes the characters the prompt uses to less plain ones (``✚`` instead of ``*`` for the dirty state for example) , and if you are only interested in that, set ``$__fish_git_prompt_use_informative_chars`` instead.
 
   Because counting untracked files requires a lot of time, the number of untracked files is only shown if enabled via ``$__fish_git_prompt_showuntrackedfiles`` or the git option ``bash.showUntrackedFiles``.
 

doc_src/cmds/jobs.rst

@@ -36,7 +36,7 @@ Description
 **-h** or **--help**
     Displays help about using this command.
 
-On systems that supports this feature, jobs will print the CPU usage of each job since the last command was executed. The CPU usage is expressed as a percentage of full CPU activity. Note that on multiprocessor systems, the total activity may be more than 100\%.
+On systems that support this feature, jobs will print the CPU usage of each job since the last command was executed. The CPU usage is expressed as a percentage of full CPU activity. Note that on multiprocessor systems, the total activity may be more than 100\%.
 
 Arguments of the form *PID* or *%JOBID* restrict the output to jobs with the selected process identifiers or job numbers respectively.
 

doc_src/cmds/math.rst

@@ -136,7 +136,7 @@ Functions
       0x1
 
 ``ceil``
-    round number up to nearest integer
+    round number up to the nearest integer
 ``cos``
     the cosine
 ``cosh``
@@ -146,7 +146,7 @@ Functions
 ``fac``
     factorial - also known as ``x!`` (``x * (x - 1) * (x - 2) * ... * 1``)
 ``floor``
-    round number down to nearest integer
+    round number down to the nearest integer
 ``ln``
     the base-e logarithm
 ``log`` or ``log10``

doc_src/cmds/realpath.rst

@@ -20,7 +20,7 @@ Description
           To see the documentation on the ``realpath`` command you might have,
           use ``command man realpath``.
 
-:program:`realpath` follows all symbolic links encountered for the provided :envvar:`PATH`, printing the absolute path resolved. :ref:`fish <cmd-fish>` provides a :command:`realpath`-alike builtin intended to be enrich systems where no such command is installed by default.
+:program:`realpath` follows all symbolic links encountered for the provided :envvar:`PATH`, printing the absolute path resolved. :ref:`fish <cmd-fish>` provides a :command:`realpath`-alike builtin intended to enrich systems where no such command is installed by default.
 
 If a :command:`realpath` command exists, that will be preferred.
 ``builtin realpath`` will explicitly use the fish implementation of :command:`realpath`.

doc_src/cmds/set_color.rst

@@ -13,7 +13,7 @@ Synopsis
 Description
 -----------
 
-``set_color`` is used to control the color and styling of text in the terminal. *VALUE* describes that styling. *VALUE* can be a reserved color name like **red** or a RGB color value given as 3 or 6 hexadecimal digits ("F27" or "FF2277"). A special keyword **normal** resets text formatting to terminal defaults.
+``set_color`` is used to control the color and styling of text in the terminal. *VALUE* describes that styling. *VALUE* can be a reserved color name like **red** or an RGB color value given as 3 or 6 hexadecimal digits ("F27" or "FF2277"). A special keyword **normal** resets text formatting to terminal defaults.
 
 Valid colors include:
 

doc_src/cmds/ulimit.rst

@@ -106,7 +106,7 @@ The ``fish`` implementation of ``ulimit`` should behave identically to the imple
 
 - Fish ``ulimit`` supports GNU-style long options for all switches.
 
-- Fish ``ulimit`` does not support the **-p** option for getting the pipe size. The bash implementation consists of a compile-time check that empirically guesses this number by writing to a pipe and waiting for SIGPIPE. Fish does not do this because it this method of determining pipe size is unreliable. Depending on bash version, there may also be further additional limits to set in bash that do not exist in fish.
+- Fish ``ulimit`` does not support the **-p** option for getting the pipe size. The bash implementation consists of a compile-time check that empirically guesses this number by writing to a pipe and waiting for SIGPIPE. Fish does not do this because this method of determining pipe size is unreliable. Depending on bash version, there may also be further additional limits to set in bash that do not exist in fish.
 
 - Fish ``ulimit`` does not support getting or setting multiple limits in one command, except reporting all values using the **-a** switch.