New fixes

Author: julitafalcondusza

docs/administration/admin_panel/roles_admin_panel.md

@@ -36,7 +36,7 @@ A user can also belong to many groups, for example, Administrators, Editors, Sub
 
 Best practice is to avoid assigning roles to users directly.
 Model your content (content types, Sections, Locations etc.) in a way that can be accessed by generic roles.
-That way system will be more secure and easier to manage.
+That way system is be more secure and easier to manage.
 This approach also improves performance. Role assignments and policies are taken into account during search/load queries.
 
 See [Permissions overview](permissions.md) for further information

docs/administration/admin_panel/system_information_admin_panel.md

@@ -5,6 +5,6 @@ description: System information provides basic system information such as versio
 # System Information
 
 The System Information panel in the back office is sourced in the [`ibexa/system-info` repository](https://github.com/ibexa/system-info).
-There you will also find basic system information such as versions of all installed packages.
+There you can also find basic system information such as versions of all installed packages.
 
 ![System Information](admin_panel_system_info.png "System Information")

docs/administration/admin_panel/users_admin_panel.md

@@ -14,4 +14,4 @@ All user groups and users can be accessed in the Admin panel by selecting **User
 !!! caution
 
     Be careful not to delete an existing user account.
-    If you do this, content created by this user will be broken and the application can face malfunction.
+    If you do this, content created by this user can be broken and the application can face malfunction.

docs/administration/back_office/back_office_elements/add_dropdowns.md

@@ -131,7 +131,7 @@ The following attributes are available:
 ### Initialize
 
 All drop-downs are searched and initialized automatically in `admin.dropdown.js`.
-To extend or modify the search, you need to add a `custom_init` attribute to the drop-down Twig parameters. Otherwise it will be initialized two times.
+To extend or modify the search, you need to add a `custom_init` attribute to the drop-down Twig parameters. Otherwise it's initialized two times.
 Next, run the following JavaScript code:
 
 ```javascript

docs/administration/back_office/back_office_elements/extending_thumbnails.md

@@ -5,7 +5,7 @@ description: Customize thumbnails use for content items in the back office.
 # Extending thumbnails
 
 The thumbnails API enable you to easily choose an image for a specific content.
-If you do not want to use custom thumbnails, `ContentType` will be used instead.
+If you do not want to use custom thumbnails, `ContentType` is used instead.
 
 ## Thumbnail mechanism 
 
@@ -25,16 +25,16 @@ For example for users thumbnails can be downloaded from an avatar-generating ser
 For this layer there are following default implementations:
 
 - The mechanism looks for Fields that can be thumbnail, if found, the mechanism moves to the second layer.
-- If there are no Fields that can be a thumbnail, the content type icon will be used as a thumbnail.
+- If there are no Fields that can be a thumbnail, the content type icon is used as a thumbnail.
 
 ### Second layer
 
 Second layer of mechanism enables selection of thumbnail from a Field that the first layer has found. 
 It searches the content type for all the Fields e.g. images with function "Can be a thumbnail" turned on.
 
-If there is more than one Field in the content type that can be used as a thumbnail, this layer will return the first nonempty Field as a thumbnail.
+If there is more than one Field in the content type that can be used as a thumbnail, this layer returns the first nonempty Field as a thumbnail.
 
-This mechanism can be modified to fit your site needs, so you can decide from where and how the thumbnails will be downloaded.
+This mechanism can be modified to fit your site needs, so you can decide from where and how the thumbnails is downloaded.
 
 ### Create a thumbnail mechanism 
 
@@ -51,7 +51,7 @@ Next, add the strategy with the `ibexa.repository.thumbnail.strategy.content` ta
 [[= include_file('code_samples/back_office/thumbnails/config/custom_services.yaml') =]]
 ```
 
-Priority `100` will allow this strategy to be used first on a clean installation or before any other strategy with lower priority.
+Priority `100` allows this strategy to be used first on a clean installation or before any other strategy with lower priority.
 
 At this point you can go to the back office and check the results.
 
@@ -69,8 +69,8 @@ Any Field Type can generate a thumbnail, e.g.:
 
 ### Add eztext Field as thumbnail
 
-First, create a strategy that will add support for `eztext` as the thumbnail.
-It will enable you to add a thumbnail URL in the text field.
+First, create a strategy that adds support for `eztext` as the thumbnail.
+It enables you to add a thumbnail URL in the text field.
 
 Add `FieldValueUrl.php` in `src/Thumbnails`.
 

docs/administration/back_office/browser/browser.md

@@ -56,17 +56,17 @@ There you can set the following properties:
 |-------------------|------|--------|----------|
 |multiple</br>`multiple`|true</br>false|no|The possibility to choose multiple Locations.|
 |multiple_items_limit</br>`multipleItemsLimit`|number|no|Maximum number of items with configuration `multiple: true`.|
-|root_location_id</br>`rootLocationId`|number|no|UDW will display Locations only below this content tree element.|
-|starting_location_id</br>`startingLocationId`|number|no|This Location will be displayed as a starting Location in UDW.|
+|root_location_id</br>`rootLocationId`|number|no|UDW displays Locations only below this content tree element.|
+|starting_location_id</br>`startingLocationId`|number|no|This Location is displayed as a starting Location in UDW.|
 |containers_only</br>`containersOnly`|true</br>false|no|When set to `true` only containers can be selected.|
 |allowed_content_types</br>`allowedContentTypes`|null</br>[]</br>[`contentTypeIdentifier`]|yes|List of allowed content types:</br>`null` – all content types are allowed,</br>`[]` – empty table, no content types are allowed.|
-|active_sort_clause</br>`activeSortClause`|DatePublished</br>ContentName|no|Sort Clause by which children in the content tree will be sorted.|
+|active_sort_clause</br>`activeSortClause`|DatePublished</br>ContentName|no|Sort Clause by which children in the content tree is sorted.|
 |active_sort_order</br>`activeSortOrder`|ascending</br>descending|no|Sorting order of the children in the content tree.|
 |active_tab</br>`activeTab`|browse</br>search</br>bookmarks|no|Starting tab in the UDW.|
 |active_view</br>`activeView`|finder</br>grid</br>tree|no|Starting view in the UDW.|
 |allow_redirects</br>`allowRedirects`|true</br>false|yes|Allows to redirect content from the UDW tab to another page, for example, to content edit page.|
-|selected_locations</br>`selectedLocations`|[]</br>[locationId]|no|Location that will be selected automatically.|
-|allow_confirmation</br>`allowConfirmation`|true</br>false|yes|Shows confirmations buttons in the UDW. If set to false, it will not be possible to confirm selection.|
+|selected_locations</br>`selectedLocations`|[]</br>[locationId]|no|Location that is selected automatically.|
+|allow_confirmation</br>`allowConfirmation`|true</br>false|yes|Shows confirmations buttons in the UDW. If set to false, it's not possible to confirm selection.|
 
 ### Content on the Fly group
 
@@ -77,7 +77,7 @@ There you can set the following properties:
 |preselected_language</br>`preselectedLanguage`|null</br>languageCode|yes|First language on the Content on the Fly language list:</br>null - language order defined in the system.|
 |preselected_content_type</br>`preselectedContentType`|null</br>contentTypeIdentifier|yes|Content selected in Content on the Fly.|
 |hidden</br>`hidden`|true</br>false|yes|Content on the Fly visibility.|
-|auto_confirm_after_publish</br>`autoConfirmAfterPublish`|true</br>false|yes|If set to `true` UDW will be automatically closed after publishing the content.|
+|auto_confirm_after_publish</br>`autoConfirmAfterPublish`|true</br>false|yes|If set to `true` UDW is automatically closed after publishing the content.|
 
 ### Tabs config group
 
@@ -125,7 +125,7 @@ ibexa:
 
 ### Add new configuration to button
 
-In the `ibexa_udw_config` Twig helper, define a specific part of YAML configuration that will be used to render the **Content Browser**.
+In the `ibexa_udw_config` Twig helper, define a specific part of YAML configuration that is used to render the **Content Browser**.
 You can find Twig helper in your button template.
 In the example below, a key is pointing to `my_custom_udw` configuration and has additional parameter `johndoe`.
 
@@ -141,7 +141,7 @@ In the example below, a key is pointing to `my_custom_udw` configuration and has
 
 ### Additional parameters
 
-If an event listener catches additional parameters passed with context, it will use a configuration specified for it in the event subscriber.
+If an event listener catches additional parameters passed with context, it uses a configuration specified for it in the event subscriber.
 
 In the example below, the `johndoe` parameter enables the user to choose multiple items from a **Browser window** by changing `multiple: false` from `my_custom_udw` configuration to `multiple: true`.
 

docs/administration/back_office/content_tree.md

@@ -19,7 +19,7 @@ ibexa:
         # any SiteAccess or SiteAccess group
         admin_group:
             content_tree_module:
-                # defines how many children will be shown after expanding parent
+                # defines how many children is be shown after expanding parent
                 load_more_limit: 15
                 # users won't be able to load more children than that
                 children_load_max_limit: 200
@@ -33,7 +33,7 @@ ibexa:
                    - article
                 # ID of Location to use as tree root. If omitted - content.tree_root.location_id setting is used.
                 tree_root_location_id: 2
-                # list of Location IDs for which content tree's root Location will be changed
+                # list of Location IDs for which content tree's root Location is changed
                 contextual_tree_root_location_ids:
                    - 2 # Home (Content structure)
                    - 5 # Users

docs/administration/back_office/notifications.md

@@ -12,7 +12,7 @@ It appears to whoever is doing a specific operation in the back office.
 ![Example of an info notification](notification2.png "Example of the notification bar")
 
 [Custom notifications](#create-custom-notifications) are sent to a specific user.
-They will appear in their profile in the back office.
+They appears in their profile in the back office.
 
 ![Notification in profile](notification3.png)
 
@@ -53,7 +53,7 @@ Dispatch the event with `document.body.dispatchEvent(eventInfo);`.
 
 ## Create custom notifications
 
-You can send your own custom notifications to the user which will be displayed in the user menu.
+You can send your own custom notifications to the user which are displayed in the user menu.
 
 To create a new notification you must use the `createNotification(Ibexa\Contracts\Core\Repository\Values\Notification\CreateStruct $createStruct)` method from `Ibexa\Contracts\Core\Repository\NotificationService`.
 

docs/administration/back_office/subitems_list.md

@@ -51,7 +51,7 @@ The `<SubItemsModule />` module can handle additional properties. There are two
 
 ### Required props
 
-Without all the following properties the Sub-items module will not work.
+Without all the following properties the Sub-items module cannot work.
 
 - **parentLocationId** _{Number}_ - parent Location ID
 - **restInfo** _{Object}_ - backend config object:

docs/administration/configuration/dynamic_configuration.md

@@ -55,8 +55,8 @@ $myParamSettingAdmin = $configResolver->getParameter( 'my_param', 'myapp', 'admi
 Both `getParameter()` and `hasParameter()` can take three arguments:
 
 1. `$paramName` - the name of the parameter
-2. `$namespace` - your application namespace, `myapp` in the previous example. If null, the default namespace will be used, which is `ibexa.site_access.config` by default.
-3. `$scope` - a SiteAccess name. If null, the current SiteAccess will be used.
+2. `$namespace` - your application namespace, `myapp` in the previous example. If null, the default namespace is used, which is `ibexa.site_access.config` by default.
+3. `$scope` - a SiteAccess name. If null, the current SiteAccess is used.
 
 ## Inject ConfigResolver into services