New fixes

Author: julitafalcondusza

docs/administration/admin_panel/segments_admin_panel.md

@@ -6,7 +6,7 @@ edition: experience
 # Segments
 
 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.
+they're used out of the box in the Targeting and Dynamic targeting blocks in the Page.
 
 Segments are collected in Segment Groups:
 

docs/administration/admin_panel/users_admin_panel.md

@@ -5,7 +5,7 @@ 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're 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**.
 

docs/administration/back_office/content_tab_switcher.md

@@ -74,7 +74,7 @@ First, create an event listener in the `src/EventListener/TextAnchorMenuTabListe
 
 A new custom tab is defined in the line 28, the line 31 defines items for the second level.
 
-For new tabs it is also required to render its section in the content editing form. To do it, register the UI Component:
+For new tabs it's also required to render its section in the content editing form. To do it, register the UI Component:
 
 ```yaml
 [[= include_file('code_samples/back_office/content_type/config/custom_services.yaml') =]]

docs/administration/back_office/content_type_anchor_menu.md

@@ -43,4 +43,4 @@ Enable the toggle to display the SEO section on the content item edit page.
 
 !!! note
 
-    If you add multiple Field Types as anchor menus, they are automatically displayed as separate sections. 
+    If you add multiple Field Types as anchor menus, they're automatically displayed as separate sections. 

docs/administration/back_office/multifile_upload.md

@@ -10,7 +10,7 @@ It provides an interface to publish content based on dropped files while uploadi
 !!! caution
 
     If you want to load the multi-file upload module, you need to load the JS code for it in your view,
-    as it is not available by default.
+    as it's not available by default.
 
 ## Use multi-file upload
 

docs/administration/back_office/subitems_list.md

@@ -10,7 +10,7 @@ It provides an interface for listing the sub-items of any Location.
 !!! caution
 
     If you want to load the Sub-items module, you need to load the JS code for it in your view,
-    as it is not available by default.
+    as it's not available by default.
 
 ## Use sub-items list
 

docs/administration/configuration/configuration.md

@@ -9,7 +9,7 @@ It contains everything from selecting the content Repository to SiteAccesses to
 
 ### Configuration format
 
-The recommended configuration format is YAML. It is used by default in the kernel (and in examples throughout the documentation).
+The recommended configuration format is YAML. It's used by default in the kernel (and in examples throughout the documentation).
 However, you can also use XML or PHP formats for configuration.
 
 ### Configuration files
@@ -29,7 +29,7 @@ These files contain additional settings and point to the general (not environmen
 
 !!! note "New configuration files"
 
-    It is good practice to provide your own configuration in separate files.
+    It's good practice to provide your own configuration in separate files.
     Any YAML files placed in the `config/packages` folder is automatically included in the system configuration.
 
 !!! tip

docs/administration/configuration/dynamic_configuration.md

@@ -77,7 +77,7 @@ You can also use the [autowire feature]([[= symfony_doc =]]/service_container/au
 
 !!! note
 
-    Do not store the retrieved config value unless you know what you are doing. 
+    Do not store the retrieved config value unless you know what you're doing. 
     SiteAccess can change during code execution, which means you might work on the wrong value.
 
 ``` php

docs/administration/configuration/repository_configuration.md

@@ -57,7 +57,7 @@ For example:
 But the following configuration would be invalid:
 
 - `ibexa.co` domain can use `ibexa_repo`
-- `ibexa.co/doc` **cannot** use `doc_repo`, as it is under the same domain.
+- `ibexa.co/doc` **cannot** use `doc_repo`, as it's under the same domain.
 
 Invalid configuration causes problems for different parts of the system,
 for example back-end UI, REST interface and other non-SiteAccess-aware Symfony routes
@@ -66,7 +66,7 @@ such as `/_fos_user_context_hash` used by [HTTP cache](http_cache.md).
 ### Entity manager
 
 If you use the [Doctrine entity manager](https://www.doctrine-project.org/projects/doctrine-orm/en/2.10/tutorials/getting-started.html#obtaining-the-entitymanager),
-you are unable to connect different SiteAccesses to different databases.
+you're unable to connect different SiteAccesses to different databases.
 
 To have this possibility, you need to use the SiteAccess-aware entity manager: `ibexa.doctrine.orm.entity_manager`.
 
@@ -184,7 +184,7 @@ user_data: User data
 ## Limit of archived content versions
 
 `default_version_archive_limit` controls the number of archived versions per content item that are stored in the Repository.
-By default it is set to 5. This setting is configured in the following way (typically in `ibexa.yaml`):
+By default it's set to 5. This setting is configured in the following way (typically in `ibexa.yaml`):
 
 ``` yaml
 ibexa:

docs/administration/content_organization/content_types.md

@@ -76,7 +76,7 @@ They determine what Fields of what Field Types will be included in all content i
 !!! caution
 
     In case of content types containing many Field Types you should be aware of possible memory-related issues with publishing/editing.
-    They are caused by the limitation of how many `$_POST` input variables can be accepted.
+    they're caused by the limitation of how many `$_POST` input variables can be accepted.
 
     The easiest way to fix them is by increasing the `max_input_vars` value in the `php.ini` configuration file.
     Note that this solution is not universally recommended and you're proceeding on your own risk.