Content updates, capitalization fixes

Author: julitafalcondusza

docs/administration/admin_panel/admin_panel.md

@@ -1,5 +1,5 @@
 ---
-description: Ibexa DXP Back Office contains managements options for permissions, users, languages, content types, as well as system information.
+description: Ibexa DXP back office contains managements options for permissions, users, languages, content types, as well as system information.
 page_type: landing_page
 ---
 

docs/administration/admin_panel/roles_admin_panel.md

@@ -1,43 +1,43 @@
 ---
-description: To give users an access to your website you need to assign them Roles in the Admin Panel.
+description: To give users an access to your website you need to assign them roles in the Admin Panel.
 ---
 
 # Roles
 
-To give users an access to your website you need to assign them Roles in the Admin Panel.
+To give users an access to your website you need to assign them roles in the Admin Panel.
 
 ![Roles](admin_panel_roles.png "Roles")
 
-Each Role consists of:
+Each role consists of:
 
 **Policies**
 
 ![Policies](admin_panel_policies.png "Policies")
 
 Rules that give users access to different function in a module.
-You can restrict what user can do with Limitations.
-The available Limitations depend on the chosen Policy.
-When Policy has more than one Limitation, all of them have to apply.
+You can restrict what user can do with limitations.
+The available limitations depend on the chosen policy.
+When policy has more than one limitation, all of them have to apply.
 See [example use case](permission_use_cases.md#restrict-editing-to-part-of-the-tree).
 
 !!! note
 
-    Limitation specifies what a User can do, not what they can't do.
-    A `Location` Limitation, for example, gives the User access to content with a specific Location, 
+    Limitation specifies what a user can do, not what they can't do.
+    A `Location` limitation, for example, gives the user access to content with a specific Location, 
     not prohibits it. See [Limitation reference](limitation_reference.md) for further information.
 
 **Assignments**
 
 ![Assignments](admin_panel_assignments.png "Assignments")
 
-After you created all Policies, you can assign the Role to Users and/or User Groups with possible additional Limitations.
-Every User or User Group can have multiple Roles.
-A User can also belong to many groups, for example, Administrators, Editors, Subscribers.
+After you created all policies, you can assign the role to users and/or user groups with possible additional limitations.
+Every user or user group can have multiple roles.
+A user can also belong to many groups, for example, Administrators, Editors, Subscribers.
 
-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.
+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.
-This approach also improves performance. Role assignments and Policies are taken into account during search/load queries.
+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
-and [Permission use cases](permission_use_cases.md) for details on how to customize access to different parts of the Back Office.
+and [Permission use cases](permission_use_cases.md) for details on how to customize access to different parts of the back office.

docs/administration/admin_panel/segments_admin_panel.md

@@ -1,11 +1,11 @@
 ---
-description: You can use Segments to display specific content to specific Users.
+description: You can use Segments to display specific content to specific users.
 edition: experience
 ---
 
 # Segments
 
-You can use Segments to display specific content to specific [Users](users.md).
+You can use Segments to display specific content to specific [ussers](users.md).
 They are used out of the box in the Targeting and Dynamic targeting blocks in the Page.
 
 Segments are collected in Segment Groups:
@@ -16,4 +16,4 @@ Each Segment Group can contain Segments that you can target content for.
 
 ![Segment](admin_panel_segment.png)
 
-You can assign Users to Segments [through the API](segment_api.md#assigning-users).
+You can assign users to Segments [through the API](segment_api.md#assigning-users).

docs/administration/admin_panel/system_information_admin_panel.md

@@ -4,7 +4,7 @@ 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).
+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.
 
 ![System Information](admin_panel_system_info.png "System Information")

docs/administration/admin_panel/users_admin_panel.md

@@ -1,17 +1,17 @@
 ---
-description: All User Groups and Users can be accessed in the Users tab.
+description: All user groups and users can be accessed in the users tab.
 ---
 
 # Users
 
 [Users](users.md) in [[= product_name =]] are treated the same way as content items.
-They are organized in groups such as *Guests*, *Editors*, *Anonymous*, 
+They are organized in groups such as *Guests*, *Editors*, *Anonymous*,
 which makes it easier to manage them and their permissions.
-All User Groups and Users can be accessed in the Admin panel by selecting Users.
+All user groups and users can be accessed in the Admin panel by selecting **Users**.
 
-![Users and User Groups](admin_panel_users.png "Users and User Groups")
+![Users and user groups](admin_panel_users.png "Users and user groups")
 
 !!! 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.
+    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.

docs/administration/back_office/add_user_setting.md

@@ -4,9 +4,9 @@ description: Add the option to select a custom preference in user menu.
 
 # Add user setting
 
-## Create new User setting
+## Create new user setting
 
-You can add new preferences to the **User Settings** menu in the Back Office.
+You can add new preferences to the **User Settings** menu in the back office.
 
 To do so, create a setting class implementing two interfaces:
 `ValueDefinitionInterface` and `FormMapperInterface`.
@@ -24,7 +24,7 @@ Register the setting as a service:
 [[= include_file('code_samples/back_office/settings/config/custom_services.yaml', 0, 5) =]]
 ```
 
-You can order the settings in the User menu by setting their `priority`.
+You can order the settings in the **User** menu by setting their `priority`.
 
 `group` indicates the group that the setting is placed in.
 It can be one of the built-in groups, or a custom one.

docs/administration/back_office/back_office.md

@@ -1,15 +1,15 @@
 ---
-description: Back Office holds the administrator and editor interface and allows creating, publishing and managing content, users, settings and so on.
+description: Back office holds the administrator and editor interface and allows creating, publishing and managing content, users, settings and so on.
 page_type: landing_page
 ---
 
-# Back Office
+# Back office
 
-The Back Office interface is produced by the [`ibexa/admin-ui` bundle](https://github.com/ibexa/admin-ui).
+The back office interface is produced by the [`ibexa/admin-ui` bundle](https://github.com/ibexa/admin-ui).
 Additionally, it uses React-based modules that make each part of the UI extensible, and Bootstrap for styling.
 The interface is accessible in your browser at `http://<yourdomain>/admin`.
 
-To extend the Back Office with PHP code, you can use [events]([[= symfony_doc =]]/event_dispatcher.html),
+To extend the back office with PHP code, you can use [events]([[= symfony_doc =]]/event_dispatcher.html),
 either built-in Symfony events or events dispatched by the application.
 
 Some extensibility, such as [adding custom tags](extend_online_editor.md#configure-custom-tags),
@@ -18,7 +18,7 @@ is possible without writing your own code, with configuration and templating onl
 !!! note "String translations"
 
     Refer to [Custom string translations](back_office_translations.md#custom-string-translations)
-    to learn how to provide string translations when extending the Back Office.
+    to learn how to provide string translations when extending the back office.
 
 [[= cards([
     "administration/back_office/back_office_configuration",

docs/administration/back_office/back_office_configuration.md

@@ -1,13 +1,13 @@
 ---
-title: Back Office configuration
-description: Configure default upload locations, pagination limits, and more settings for the Back Office.
+title: Back office configuration
+description: Configure default upload locations, pagination limits, and more settings for the back office.
 ---
 
-# Back Office configuration
+# Back office configuration
 
 ## Pagination limits
 
-Default pagination limits for different sections of the Back Office can be defined through respective settings in
+Default pagination limits for different sections of the back office can be defined through respective settings in
 [`ezplatform_default_settings.yaml`](https://github.com/ibexa/admin-ui/blob/main/src/bundle/Resources/config/ezplatform_default_settings.yaml#L7)
 
 You can set the pagination limit for user settings under the `ibexa.system.<scope>.pagination_user` [configuration key](configuration.md#configuration-files):

docs/administration/back_office/back_office_elements/add_drag_and_drop.md

@@ -1,10 +1,10 @@
 ---
-description: Add custom drag-and-drop interactions to Back Office interface.
+description: Add custom drag-and-drop interactions to back office interface.
 ---
 
 # Add drag and drop
 
-You can create a generic interface for drag and drop interactions that you can reuse in many places across the Back Office.
+You can create a generic interface for drag and drop interactions that you can reuse in many places across the back office.
 
 First, prepare the HTML code structure and place it in a Twig template. See the example:
 

docs/administration/back_office/back_office_elements/add_dropdowns.md

@@ -1,10 +1,10 @@
 ---
-description: Add custom drop down menus to Back Office interface.
+description: Add custom drop down menus to back office interface.
 ---
 
 # Add drop-downs
 
-In [[= product_name =]], you can create a reusable custom drop-down and implement it anywhere in the Back Office.
+In [[= product_name =]], you can create a reusable custom drop-down and implement it anywhere in the back office.
 Follow the steps below to learn how to integrate this component to fit it to your project needs.
 
 ## Create `<select>` input