Fixed several typos and grammar errors

Signed-off-by: Andrew Dawes <andrewsdawes@gmail.com>

admin_manual/configuration_server/background_jobs_configuration.rst

@@ -107,7 +107,7 @@ Which returns::
 
 .. note:: On some systems it might be required to call **php-cli** instead of **php**.
 
-.. note:: For some configurations, it might be neccessary to append ``--define apc.enable_cli=1`` to the cron command. Please refer to :doc:`./caching_configuration` (section APCu).
+.. note:: For some configurations, it might be necessary to append ``--define apc.enable_cli=1`` to the cron command. Please refer to :doc:`./caching_configuration` (section APCu).
 
 .. note:: Please refer to the crontab man page for the exact command syntax.
 

admin_manual/configuration_user/profile_configuration.rst

@@ -88,4 +88,4 @@ If you'd like to override the value for one or several default visibility scopes
     \OCP\Accounts\IAccountManager::PROPERTY_ROLE => \OCP\Accounts\IAccountManager::SCOPE_FEDERATED
   ]
 
-In the above example, the phone and role properties are respectively overritten to the private and federated scopes. Note that these changes will only apply to *new* users, not existing ones.
+In the above example, the phone and role properties are respectively overwritten to the private and federated scopes. Note that these changes will only apply to *new* users, not existing ones.

admin_manual/configuration_user/two_factor-auth.rst

@@ -39,7 +39,7 @@ By default 2FA is *optional*, hence users are given the choice whether to enable
 it for their account. Admins may enforce the use of 2FA.
 
 
-Enforcement is possible systemwide (all users), for selected groups only and can
+Enforcement is possible system-wide (all users), for selected groups only and can
 also be excluded for certain groups.
 
 

admin_manual/configuration_user/user_configuration.rst

@@ -206,7 +206,7 @@ Deleting users
 
 Deleting a user is easy: hover your cursor over their name on the **Users** page
 until the "..."-menu icon appears at the far right. After clicking on it, you will
-see the **Delete** option. Clicking on it, delets a user with all their data immediately.
+see the **Delete** option. Clicking on it, deletes a user with all their data immediately.
 
 You'll see an undo button at the top of the page, which remains for some seconds.
 When the undo button is gone you cannot recover the deleted user.

admin_manual/gdpr/cookies.rst

@@ -28,5 +28,5 @@ Cookies stored by Nextcloud
                        - remember token                       
 ====================  ====================================  ================
 
-The same-site cookies are used to determine how a request reaches the Nextcloud server. We use them to prevent CSRF attacks. No identifable information is stored in those.
+The same-site cookies are used to determine how a request reaches the Nextcloud server. We use them to prevent CSRF attacks. No identifiable information is stored in those.
 The rest of the cookies are strictly used to identify the user to the system.

admin_manual/installation/system_requirements.rst

@@ -55,7 +55,7 @@ Database requirements for MySQL / MariaDB
 The following is currently required if you're running Nextcloud together with a MySQL / MariaDB database:
 
 * InnoDB storage engine (MyISAM is not supported)
-* "READ COMMITED" transaction isolation level (See: :ref:`db-transaction-label`)
+* "READ COMMITTED" transaction isolation level (See: :ref:`db-transaction-label`)
 * Disabled or BINLOG_FORMAT = ROW configured Binary Logging (See: https://dev.mysql.com/doc/refman/5.7/en/binary-log-formats.html)
 * For **Emoji (UTF8 4-byte) support** see :doc:`../configuration_database/mysql_4byte_support`
 

admin_manual/maintenance/manual_upgrade.rst

@@ -72,7 +72,7 @@ Always start by making a fresh backup and disabling all 3rd party apps.
     size of your installation. When it is finished you will see a success 
     message, or an error message that will tell where it went wrong.
 
-15. Reenable the nextcloud cron-job. (See step 4 above.)
+15. Re-enable the nextcloud cron-job. (See step 4 above.)
 
      crontab -u www-data -e
 

admin_manual/maintenance/migrating.rst

@@ -24,7 +24,7 @@ the new location. It is also assumed that the authentication method
 .. warning:: At NO TIME any changes to the **ORIGINAL** system are required
     **EXCEPT** putting Nextcloud into maintenance mode.
 
-    This ensures, should anything unforseen happen you can go
+    This ensures, should anything unforeseen happen you can go
     back to your existing installation and provide your users
     with a running Nextcloud while debugging the problem.
 

admin_manual/maintenance/update.rst

@@ -76,7 +76,7 @@ steps:
     a new update available. Go to the admin settings page and scroll to the
     section "Version". This section has a button to open the updater. This
     section as well as the update notification is only available if the update
-    notication app is enabled in the apps management.
+    notification app is enabled in the apps management.
 
 .. figure:: images/updater-1-update-available.png
 

admin_manual/office/migration.rst

@@ -15,7 +15,7 @@ Due to naming changes in the Collabora Online releases it may be required to adj
 - Paths with ``lool`` have been renamed to ``cool``
 - Paths with ``loleaflet`` have been renamed to ``browser``
 
-Fully detailed reverse proxy configration guides for various solutions can be found at https://sdk.collaboraonline.com/docs/installation/Proxy_settings.html
+Fully detailed reverse proxy configuration guides for various solutions can be found at https://sdk.collaboraonline.com/docs/installation/Proxy_settings.html
 
 Upgrade distribution packages
 *****************************

developer_manual/app_development/bootstrap.rst

@@ -4,7 +4,7 @@
 Bootstrapping
 =============
 
-Every php process has a relatively short lifespan that lasts as long as the HTTP request or the invokation of the command
+Every php process has a relatively short lifespan that lasts as long as the HTTP request or the invocation of the command
 line program. At the beginning of this lifespan, Nextcloud initializes its services. At the same time, any additional apps
 might want to register their services to Nextcloud as well. This event is called the *bootstrapping* and this chapter
 shall shed some light on how to hook into this with an app.
@@ -101,14 +101,14 @@ Nextcloud 20 and later
 
 Nextcloud 20 is the first release with the interface ``\OCP\AppFramework\Bootstrap\IBootstrap``. This interface can be
 implemented by your app's ``Application`` class to signal that it wants to act on the bootstrapping stages. The major difference
-between this and the old process is that the boostrapping is not performed in sequence, but apps register and boot
+between this and the old process is that the bootstrapping is not performed in sequence, but apps register and boot
 interleaved. This should ensure that an app that ``boot``\s can rely on all other apps' registration to be finished.
 
 The overall process is as follows:
 
 1) In each installed and enabled app that has an ``Application`` class that also implements ``IBootstrap``, the ``register``
    method will be called. This method receives a context argument via which the app can prime the dependency injection
-   container and register other services lazily, e.g. by calling ``$context->registerService(...)``. The emphasis is on **lazyness**. At this very early stage of the
+   container and register other services lazily, e.g. by calling ``$context->registerService(...)``. The emphasis is on **laziness**. At this very early stage of the
    process lifetime, no other apps nor all of the server components are ready. Therefore the app **must not** try to use
    anything except the API provided by the context. That shall ensure that all apps can safely run their registration logic
    before any services are queried (instantiated) from the DI container or related code is run.
@@ -123,7 +123,7 @@ Nextcloud 19 and older
 
 Nextcloud will load groups of certain apps early, like filesystem or session apps, and other later. For this their optional
 :ref:`app-php` will be included. The ``Application`` class is only queried for some requests, so there is no guarantee that
-its contstructor will be invoked.
+it's constructor will be invoked.
 
 
 .. _app-php:

developer_manual/app_development/dependency_management.rst

@@ -11,7 +11,7 @@ It's possible to build a Nextcloud app with existing software packages.
 Composer
 --------
 
-You can add 3rd party php packages with `Composer`_. Composer will download the specified packages to a directory of your choise, typically to ``/vendor``. In order to benefit from Composer's autoloader, you'll want to add a ``require_once`` to the ``register`` method of your ``Application`` class in the :ref:`bootstrapping<Bootstrapping>` code of your app.
+You can add 3rd party php packages with `Composer`_. Composer will download the specified packages to a directory of your choice, typically to ``/vendor``. In order to benefit from Composer's autoloader, you'll want to add a ``require_once`` to the ``register`` method of your ``Application`` class in the :ref:`bootstrapping<Bootstrapping>` code of your app.
 
 .. note:: Be careful with which packages you add to an app. Php can not load two version of the same class twice, hence there can be conflicts between Nextcloud Server and an app or between two or more apps if they ship the same library. So try to keep the number of libraries to a minimum.
 

developer_manual/basics/controllers.rst

@@ -558,7 +558,7 @@ A file download can be triggered by returning a DownloadResponse:
 Creating custom responses
 ^^^^^^^^^^^^^^^^^^^^^^^^^
 
-If no premade Response fits the needed usecase, it is possible to extend the Response base class and custom Response. The only thing that needs to be implemented is the **render** method which returns the result as string.
+If no premade Response fits the needed use case, it is possible to extend the Response base class and custom Response. The only thing that needs to be implemented is the **render** method which returns the result as string.
 
 Creating a custom XMLResponse class could look like this:
 
@@ -716,7 +716,7 @@ In order to ease migration from OCS API routes to the App Framework, an addition
 
 The format parameter works out of the box, no intervention is required.
 
-In order to make routing work for OCS routes you need to add a seperate 'ocs' entry to the routing table of your app.
+In order to make routing work for OCS routes you need to add a separate 'ocs' entry to the routing table of your app.
 Inside these are normal routes.
 
 .. code-block:: php

developer_manual/basics/events.rst

@@ -30,7 +30,7 @@ The name should reflect the subject and the actions. Suffixing event classes wit
 
 For example, if a user is created, a `UserCreatedEvent` will be emitted.
 
-Events are ususally evmitted *after* the event has happened. If it's emitted before, it should be prefixed with `Before`.
+Events are usually evmitted *after* the event has happened. If it's emitted before, it should be prefixed with `Before`.
 
 Thus `BeforeUserCreatedEvent` is emitted *before* the user data is written to the database.
 
@@ -339,7 +339,7 @@ This event is triggered when a federated share is successfully added.
 
 *Available in Nextcloud 17 and later.*
 
-This event is triggered when the files app is rendered. It canb e used to add additional scripts to the files app.
+This event is triggered when the files app is rendered. It can be used to add additional scripts to the files app.
 
 ``\OCA\Files_Sharing\Event\BeforeTemplateRenderedEvent``
 ********************************************************
@@ -555,7 +555,7 @@ Emitted before a user is logged in via remember-me cookies.
 
 *Available in Nextcloud 18 and later.*
 
-Emitted when a user has been succesfully logged in via remember-me cookies.
+Emitted when a user has been successfully logged in via remember-me cookies.
 
 ``\OCP\User\Events\BeforePasswordUpdatedEvent``
 ***********************************************
@@ -681,7 +681,7 @@ Hooks are used to execute code before or after an event has occurred. This is fo
     $app = new Application();
     $app->getContainer()->query('UserHooks')->register();
 
-The hook logic should be in a separate class that is being registered in the `App contructor <dependency_injection.html#using-a-container>`__:
+The hook logic should be in a separate class that is being registered in the `App constructor <dependency_injection.html#using-a-container>`__:
 
 .. code-block:: php
 

developer_manual/client_apis/android_library/examples.rst

@@ -256,7 +256,7 @@ Code example
 Move a file or folder
 ---------------------
 
-Move an exisintg file or folder to a different location in the Nextcloud server. Parameters needed are the path
+Move an existing file or folder to a different location in the Nextcloud server. Parameters needed are the path
 to the file or folder to move, and the new path desired for it. The parent folder of the new path must exist in
 the server.
 

developer_manual/client_apis/android_library/library_installation.rst

@@ -36,7 +36,7 @@ and add the dependency::
 
   compile 'com.github.nextcloud:android-library:<version>'
 
-<version> refers to the exact version you would like to include in your application. This could be -SNAPSHOT for always using the latest code revision of the master branch. Alternatively you can also specifiy a version number which refers to a fixed release, e.g. 1.0.0. (compile 'com.github.nextcloud:android-library:1.0.0').
+<version> refers to the exact version you would like to include in your application. This could be -SNAPSHOT for always using the latest code revision of the master branch. Alternatively you can also specify a version number which refers to a fixed release, e.g. 1.0.0. (compile 'com.github.nextcloud:android-library:1.0.0').
 
 
 Add the library project to your project as a Git submodule

developer_manual/core/unit-testing.rst

@@ -100,7 +100,7 @@ adjust your php.ini and file rights.
 Running unit tests for the Nextcloud core project
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 The core project provides core unit tests using different database backends like sqlite, mysql, pgsql, oci (for Oracle).
-Every database to test needs to accesible either
+Every database to test needs to accessible either
 
 - natively, setup with
 

developer_manual/design/atomiccomponents.rst

@@ -73,7 +73,7 @@ Some commonly used actions in the action menu are favoriting, renaming, download
 It is important to keep the action menu simple and its length at a minimum. Too many entries in the action menu can lead to confusion and people not finding what they are looking for.
 
 .. image:: ../images/action-menu-icon.png
-   :alt: Action menu with a paperclipicon for attachments in Talk
+   :alt: Action menu with a paperclip icon for attachments in Talk
 
 In most cases the action menu is accessed through a 3-dot menu. In certain cases, it is better to use a specific icon instead of the generic 3-dot icon. For example in Talk a paperclip icon is used for accessing the action menu for attaching an item, and a heading icon is used in Text formatting bar for heading level selection.
 
@@ -238,7 +238,7 @@ Progress bars shows progress for a potentially lengthy process such as uploading
 
 The progress bar component is also sometimes used as a meter to visualize data as seen in the settings for Files to show the quota.
 
-`Progess bar Vue component <https://nextcloud-vue-components.netlify.app/#/Components/ProgressBar>`_.
+`Progress bar Vue component <https://nextcloud-vue-components.netlify.app/#/Components/ProgressBar>`_.
 
 .. _User bubbles:
 

developer_manual/digging_deeper/continuous_integration.rst

@@ -113,7 +113,7 @@ Static analysis
         </issueHandlers>
     </psalm>
 
-.. Note:: The definition supresses usages of the global and static class ``OC`` like ``\OC::$server``, which is discouraged but still found in some apps. The doctrine supression is currently necessary as the database mappers and schema abstractions leak some of the 3rd party libraries of Nextcloud that are not known to Psalm.
+.. Note:: The definition suppresses usages of the global and static class ``OC`` like ``\OC::$server``, which is discouraged but still found in some apps. The doctrine supression is currently necessary as the database mappers and schema abstractions leak some of the 3rd party libraries of Nextcloud that are not known to Psalm.
 
 
 You can put this process into a GitHub Action that is run for every pull request.

developer_manual/html_css_design/css.rst

@@ -65,7 +65,7 @@ This allows us to invert the colors of the SVGs when using the dark theme.
 More information about the :ref:`svg color api <svgcolorapi>`.
 
 
-The ``icon-black-white`` mixin is a shortand for the ``icon-color`` function but it generates two sets of icons with the suffix ``-white`` and without (default black).
+The ``icon-black-white`` mixin is a shorthand for the ``icon-color`` function but it generates two sets of icons with the suffix ``-white`` and without (default black).
 
 
 .. code-block:: scss

developer_manual/html_css_design/icons.rst

@@ -19,7 +19,7 @@ White icons only have a grey background on this documentation page for readabili
 Svg color api
 =============
 
-More informations about scss and this api: :ref:`scss mixins and functions <cssicons>`
+More information about scss and this api: :ref:`scss mixins and functions <cssicons>`
 
 You can request and color any svg icons used in nextcloud with this api.
 The server will directly change the colours of the ``circle``, ``rect`` and ``path`` elements in the svg you provide.

developer_manual/html_css_design/popovermenu.rst

@@ -92,7 +92,7 @@ Technical details
 * The required **right** distance to the border (or padding, whatever you want to use) of the three-dot icon should be 14px (5 for menu margin and 6 for arrow position)
 * The ``span`` element **must** have the ``menuitem`` class.
 * The checkbox/radio must use the :ref:`nextcloud custom <checkboxes-and-radios>`
-* The form element is optionnal if you're using inputs.
+* The form element is optional if you're using inputs.
 * Supported inputs are all text based ones and buttons type ones
 
 .. image:: ../images/popover-position.png

user_manual/files/transfer_ownership.rst

@@ -3,7 +3,7 @@ Transfer Ownership
 ==================
 
 Users can transfer the ownership of files and folders to other users. Sharing 
-ownerships of those transfered files/folders will also be transferred.
+ownerships of those transferred files/folders will also be transferred.
 
 #. Navigate to *Settings* > *Personal* > *Sharing* > *Files*.
 #. Click on *Choose file or folder to transfer* >> A file picker opens, showing all files and folders in the user's account.