oroinc
diff --git a/‎api/index.rst
+1-1 b/‎api/index.rst
+1-1
diff --git a/‎backend/api/storefront-routes.rst
-2 b/‎backend/api/storefront-routes.rst
-2
diff --git a/‎backend/api/storefront.rst
-2 b/‎backend/api/storefront.rst
-2
diff --git a/‎backend/architecture/custom-application.rst
+5-7 b/‎backend/architecture/custom-application.rst
+5-7
diff --git a/‎backend/architecture/customization/index.rst
+1-1 b/‎backend/architecture/customization/index.rst
+1-1
diff --git a/‎backend/architecture/differences.rst
+1-1 b/‎backend/architecture/differences.rst
+1-1
diff --git a/‎backend/architecture/framework/index.rst
+1-1 b/‎backend/architecture/framework/index.rst
+1-1
diff --git a/‎backend/architecture/index.rst
+3-3 b/‎backend/architecture/index.rst
+3-3
diff --git a/‎backend/architecture/structure/index.rst
+1-1 b/‎backend/architecture/structure/index.rst
+1-1
diff --git a/‎backend/automated-tests/debug-behat-tests.rst
-3 b/‎backend/automated-tests/debug-behat-tests.rst
-3
diff --git a/‎backend/automated-tests/functional.rst
+1-1 b/‎backend/automated-tests/functional.rst
+1-1
diff --git a/‎backend/automated-tests/index.rst
+1-1 b/‎backend/automated-tests/index.rst
+1-1
diff --git a/‎backend/configuration/yaml/datagrids.rst
+1-1 b/‎backend/configuration/yaml/datagrids.rst
+1-1
diff --git a/‎backend/cron.rst
+1-1 b/‎backend/cron.rst
+1-1
diff --git a/‎backend/dashboards/index.rst
+1-1 b/‎backend/dashboards/index.rst
+1-1
diff --git a/‎backend/emails/index.rst
+1-1 b/‎backend/emails/index.rst
+1-1
diff --git a/‎backend/entities-data-management/data-audit.rst
+1-1 b/‎backend/entities-data-management/data-audit.rst
+1-1
diff --git a/‎backend/entities-data-management/index.rst
+1-1 b/‎backend/entities-data-management/index.rst
+1-1
diff --git a/‎backend/entities/customize-crud.rst
+1-1 b/‎backend/entities/customize-crud.rst
+1-1
diff --git a/‎backend/entities/customize-datagrids/backend/extensions/mass-action.rst
-1 b/‎backend/entities/customize-datagrids/backend/extensions/mass-action.rst
-1
diff --git a/‎backend/entities/index.rst
+1-1 b/‎backend/entities/index.rst
+1-1
diff --git a/‎backend/entities/migration.rst
-3 b/‎backend/entities/migration.rst
-3
diff --git a/‎backend/extend-crm/how-to-co-install-applications.rst ‎backend/extend-commerce/how-to-co-install-applications.rst b/‎backend/extend-crm/how-to-co-install-applications.rst ‎backend/extend-commerce/how-to-co-install-applications.rst
diff --git a/‎backend/extend-commerce/index.rst
+6-5 b/‎backend/extend-commerce/index.rst
+6-5
diff --git a/‎backend/extend-crm/index.rst
-14 b/‎backend/extend-crm/index.rst
-14
diff --git a/‎backend/extension/add-extension.rst
+1-1 b/‎backend/extension/add-extension.rst
+1-1
diff --git a/‎backend/extension/index.rst
+2-2 b/‎backend/extension/index.rst
+2-2
diff --git a/‎backend/feature-toggle/index.rst
+1-1 b/‎backend/feature-toggle/index.rst
+1-1
diff --git a/‎backend/index.rst
-2 b/‎backend/index.rst
-2
diff --git a/‎backend/logging/index.rst
+1-1 b/‎backend/logging/index.rst
+1-1
diff --git a/‎backend/mq/index.rst
+1-1 b/‎backend/mq/index.rst
+1-1
diff --git a/‎backend/navigation/index.rst
+2-2 b/‎backend/navigation/index.rst
+2-2
diff --git a/‎backend/organization-types/index.rst
+1-1 b/‎backend/organization-types/index.rst
+1-1
diff --git a/‎backend/scopes/index.rst
+1-1 b/‎backend/scopes/index.rst
+1-1
diff --git a/‎backend/security/index.rst
+1-1 b/‎backend/security/index.rst
+1-1
@@ -1,6 +1,6 @@
 :oro_show_local_toc: false
 
-:title: OroCommerce and OroCRM Web API Development
+:title: Oro Application Web API Development
 
 .. meta::
    :description: WebAPI engine architecture and backend developer guides
 
@@ -1,5 +1,3 @@
-:oro_documentation_types: OroCommerce
-
 .. _web-api--storefront-routes:
 
 Storefront Routes
 
@@ -1,5 +1,3 @@
-:oro_documentation_types: OroCommerce
-
 .. _web-api--storefront:
 
 Storefront REST API
 
@@ -9,21 +9,19 @@ Custom Oro Application
 
 No two businesses are alike. This motto is part of Oro's product philosophy, which is why flexibility is one of
 the fundamental principles driving architecture. Depending on what you are planning to build, you can
-create your custom application with minimum functions starting either with |OroPlatform|, or |OroCRM|, or
-|OroCommerce| application as a baseline. No matter what is your starting point, there is no difference
-in the customization process.
+create your custom application with minimum functions starting with the |OroCommerce| application as a baseline.
 
 Application Repository and Installation
 ---------------------------------------
 
 Before you start working on a new project, it is essential to have a version control system in place.
-The easiest way to start is to |fork application repository| of |OroPlatform|, |OroCRM| or |OroCommerce| on GitHub.
+The easiest way to start is to |fork application repository| of |OroCommerce| on GitHub.
 
 Once code repository is ready, please follow :ref:`installation <installation>` instructions.
 
 .. note::
 
-    A newly created application repository should be used instead of the |https://github.com/orocrm/crm-application.git|
+    A newly created application repository should be used instead of the |https://github.com/oroinc/orocommerce-application.git|
 
 You can use development mode to work on customizations when your application is up and running. To warm up the
 application cache in development mode, please run:
@@ -33,15 +31,15 @@ application cache in development mode, please run:
         php bin/console cache:clear --env=dev
 
 To access the application in development mode, add `index_dev.php` to the base URL
-(example: ``http://orocrm.example.com/index_dev.php``).
+(example: ``http://orocommerce.example.com/index_dev.php``).
 
 .. _application-custom-code:
 
 Application Custom Code
 -----------------------
 
 Oro application structure is based on |Symfony Standard Edition| and we highly recommend to follow
-|Symfony Best Practices| for any custom application you build on top of OroPlatform, OroCRM, or OroCommerce.
+|Symfony Best Practices| for any custom application you build on top OroCommerce.
 
 In the root folder of your application, there is an `src` folder. Use it as a working directory
 for your custom project and put your custom code there. Like in Symfony applications, all custom code in the Oro application
 
@@ -201,7 +201,7 @@ Once your customization is ready, you can publish it in a dedicated repository t
 Customize via UI
 ^^^^^^^^^^^^^^^^
 
-For data model and business process customization, Oro applications provide the entity and workflow management tools in the web UI (e.g., OroCRM and OroCommerce back-office). You can use these tools for quick updates of the existing data structure, for example, to add a new field to the existing entity data, change the value options, etc.) and enable easy and fast prototyping, for example, for A/B testing of new business process automation.
+For data model and business process customization, Oro applications provide the entity and workflow management tools in the web UI (e.g., OroCommerce back-office). You can use these tools for quick updates of the existing data structure, for example, to add a new field to the existing entity data, change the value options, etc.) and enable easy and fast prototyping, for example, for A/B testing of new business process automation.
 
 .. warning:: Results of the customization via UI are stored in the database. Porting such customization from staging to the production environment happens on the database level using data migration. Compared to programmatic customization, customization via UI lacks versioning and portability. Please consider using the source code level customization to keep the upgrade process simple.
 
 
@@ -3,7 +3,7 @@
 Differences to Common Symfony Applications
 ==========================================
 
-Starting your first project using OroPlatform or OroCRM will be easy if you're familiar with building Symfony applications from scratch. However,
+Starting your first project using OroPlatform will be easy if you're familiar with building Symfony applications from scratch. However,
 there are some differences you need to understand to develop your application efficiently.
 
 This article will give you a short overview of how OroPlatform differs from typical Symfony applications. Each section will link to other resources where you can learn more about a particular feature.
 
@@ -88,7 +88,7 @@ Related Cookbook Articles
 * :ref:`Create Custom Oro Application <dev-cookbook-create-custom-oro-application>`
 * :ref:`Create a Simple CRUD <dev-cookbook-framework-create-simple-crud>`
 * :ref:`How to Create a New Bundle <dev-cookbook-framework-how-to-create-new-bundle>`
-* :ref:`How to Add an Extension to the OroCRM Extensions Store <dev-cookbook-framework-how-to-add-extension-to-marketplace>`
+* :ref:`How to Add an Extension to the Oro Extensions Store <dev-cookbook-framework-how-to-add-extension-to-marketplace>`
 * :ref:`How to Manage OroPlatform Extensions <dev-cookbook-framework-how-to-manage-extensions>`
 
 .. toctree::
 
@@ -1,7 +1,7 @@
-:title: OroCommerce, OroCRM, OroPlatform Architecture Developer Guide
+:title: Oro Application Architecture Developer Guide
 
 .. meta::
-   :description: Fundamentals of the OroCommerce, OroCRM, and OroPlatform applications architecture for the backend developers
+   :description: Fundamentals of the Oro applications architecture for the backend developers
 
 .. _architecture-guide:
 
@@ -23,7 +23,7 @@ With these out-of-the-box benefits, developers can focus on implementing their u
 Oro Licensing
 ~~~~~~~~~~~~~
 
-Community versions of OroCRM and OroCommerce are distributed under the |OSL-3.0| license. The community edition of OroPlatform is distributed under the |MIT| license. Enterprise editions of OroCRM, OroCommerce, and OroPlatform are distributed under a custom End User License Agreement.
+Community versions of Oro applications are distributed under the |OSL-3.0| license. The community edition of OroPlatform is distributed under the |MIT| license. Enterprise editions of Oro applications are distributed under a custom End User License Agreement.
 
 .. _architecture-overview:
 
 
@@ -28,7 +28,7 @@ Sample applications: |OroCRM|, |OroCommerce|, |OroPlatform|.
 
 A **package** repository contains a module that groups a set of ready-to-use features, usually those related to a particular business subdomain, and may be included in any Oro application. To enable an Oro package in the Oro application, add it as a dependency/prerequisite before you start the Oro application installation. As long as the Oro application uses the Symfony framework, packages may contain |Bundles|.
 
-For example, the |Marketing| package is, by default, enabled in OroCRM and OroCommerce applications.
+For example, the |Marketing| package is, by default, enabled in Oro applications.
 
 A component repository contains the source code of the reusable development module that enables a set of commonly used functions that you can use as third-party libraries without the Oro application. Rather than a complete business feature, the Oro component can handle generic functionality that is not bound to the business domain. Component repositories are typically published as read-only subtree distributions of independent package bundles or components.
 
 
@@ -51,7 +51,6 @@ Behat can integrate with debugging tools like Xdebug or Zend Debugger. By config
 An example of setting up a debugging environment:
 
 .. image:: /img/backend/tests/behat_configuration.png
-    :scale: 70
     :alt: Behat configuration
 
 Running a Group of Behat Tests
@@ -60,7 +59,6 @@ Running a Group of Behat Tests
 You can also run a group of tests. For this purpose, mark them with the right tag (for example, @failed-behat-test) and run the test with it.
 
 .. image:: /img/backend/tests/behat_configuration_with_tag.png
-    :scale: 73
     :alt: Behat configuration with tag
 
 Taking Screenshots
@@ -135,5 +133,4 @@ Debugging behat tests is an essential skill for ensuring the reliability and eff
 .. hint:: The screenshots created during failed Behat tests include the cursor the last position mouse when moving the mouse around, except for situations when there are alerts on the page. This helps identify where the failure occurred, making it quicker to take corrective action.
 
     .. image:: /img/backend/tests/cursor_position_at_failed_behat_tests.png
-        :scale: 55
         :alt: Cursor position at failed behat tests
@@ -354,7 +354,7 @@ Types of Functional Tests
 Testing Controllers
 ^^^^^^^^^^^^^^^^^^^
 
-Have a look at an example of a controller test from OroCRM:
+Have a look at an example of a controller test from an Oro application:
 
 .. code-block:: php
    :caption: src/OroCRM/Bundle/TaskBundle/Tests/Functional/Controller/TaskControllersTest.php
 
@@ -1,7 +1,7 @@
 .. index::
     single: Testing; Functional Testing
 
-:title: Automated Tests Implementation in OroCommerce, OroCRM, OroPlatform
+:title: Automated Tests Implementation in Oro Applications
 
 .. meta::
    :description: Principles of writing functional tests in the preconfigured testing environment with detailed guidance and examples
 
@@ -540,7 +540,7 @@ min_length
 
 type: ``integer`` default: ``0``
 
-Specify the minimum length of the search string. When the search string length is below the limit, OroCRM shows a validation message to the user and ignores the filter value.
+Specify the minimum length of the search string. When the search string length is below the limit, Oro application shows a validation message to the user and ignores the filter value.
 
 order
 ~~~~~
 
@@ -1,4 +1,4 @@
-:title: Cron Setup and Configuration in OroCommerce, OroCRM, OroPlatform
+:title: Cron Setup and Configuration in Oro Applications
 
 .. meta::
     :description: Instructions on the time-based cron jobs setup and configuration in the Oro applications for the backend developers
 
@@ -1,7 +1,7 @@
 :title: Dashboards Management in the Oro Applications Backend
 
 .. meta::
-   :description: Dashboards and widgets management guide for the OroCommerce, OroCRM, OroPlatform backend developers
+   :description: Dashboards and widgets management guide for the Oro application backend developers
 
 .. _dev-dashboards:
 
 
@@ -1,4 +1,4 @@
-:title: Backend Emails Configuration in OroCommerce, OroCRM, OroPlatform
+:title: Backend Emails Configuration in Oro Application
 
 .. meta::
     :description: Emails and templates configuration manuals for the backend developers
 
@@ -47,7 +47,7 @@ Additional Fields
 
 You can store additional fields in every entry of the audit log. There are no requirements for the type of data. If the object is passed to an array, it is properly sanitized and converted to the supported format. To clarify the need for additional fields, see the example below:
 
-Suppose you create an extension that integrates OroCRM with an external System A. This integration synchronizes Question entities between systems. However, the identifier of the Question entity is different in CRM (**id**) and System A (**subject**). System A tracks changes in CRM calling API audit endpoint and matches Questions on its side by subject, so it will be helpful to attach this field to every response (for example, when a Question is removed). To make it happen, one can use "additional fields". The entity must implement *AuditAdditionalFieldsInterface*.
+Suppose you create an extension that integrates Oro application with an external System A. This integration synchronizes Question entities between systems. However, the identifier of the Question entity is different in Oro application (**id**) and System A (**subject**). System A tracks changes in Oro application calling API audit endpoint and matches Questions on its side by subject, so it will be helpful to attach this field to every response (for example, when a Question is removed). To make it happen, one can use "additional fields". The entity must implement *AuditAdditionalFieldsInterface*.
 
 In our example, it can look like this:
 
 
@@ -1,4 +1,4 @@
-:title: Entities Data Management in OroCommerce, OroCRM, OroPlatform
+:title: Entities Data Management in Oro Application
 
 .. meta::
    :description: Entities data management guides for the backend developers
 
@@ -24,7 +24,7 @@ For example, let's add a new text field to the product edit and view screens fro
 Prerequisites
 ^^^^^^^^^^^^^
 
-Before writing code, create a new bundle in your application. If you are not familiar with the bundle creation process yet,  check :ref:`how to create a new bundle in OroPlatform, OroCRM, or OroCommerce <how-to-create-new-bundle>`. If you have already created a bundle for your app customizations, you are good to go and can reuse it in other tutorials as well.
+Before writing code, create a new bundle in your application. If you are not familiar with the bundle creation process yet,  check :ref:`how to create a new bundle in your Oro application <how-to-create-new-bundle>`. If you have already created a bundle for your app customizations, you are good to go and can reuse it in other tutorials as well.
 
 Custom Data Entity
 ~~~~~~~~~~~~~~~~~~
 
@@ -247,7 +247,6 @@ Alternatively, you can configure a mass action with operations. See :ref:`Operat
 6. View results on the ``/admin/users`` page.
 
     .. image:: /img/backend/entities/datagrid_mass_action_grid.png
-       :scale: 100%
        :alt: Mass action button on a grid toolbar
 
 Register Custom Mass Action Type
 
@@ -1,4 +1,4 @@
-:title: Entities Management in OroCommerce, OroCRM, OroPlatform
+:title: Entities Management in Oro Application
 
 .. meta::
    :description: A step by step tutorial for entities management in the Oro applications for the backend developers
 
@@ -298,9 +298,6 @@ Here is a list of available extensions:
 * |PaymentTermExtension| - Adds payment term association to the entity.
 
 * |SlugExtension| - Adds slugs to the entity. More information is available in the :ref:`RedirectBundle documentation <bundle-docs-commerce-redireect-bundle-migration-extension>`.
-
-**CRM**
-
 * |CustomerExtension| - Adds association between the target customer table and the customer table. More information is available in the :ref:`Migration Extension documentation <bundle-docs-crm-sales-bundle-migration-extension>`.
 
 **Platform**
 
@@ -1,15 +1,16 @@
-:title: Extending OroCommerce
+:title: Extending Oro Application
 
 .. meta::
-   :description: Best practices on extending the OroCommerce functionality on the Oro applications
+   :description: Best practices on extending the Oro application functionality
 
 .. _dev-extend-commerce:
 
-Extending OroCommerce
-=====================
+Extending Oro Application
+=========================
 
 .. toctree::
    :maxdepth: 1
 
    payment/index
-   shipping
+   shipping
+   how-to-co-install-applications
@@ -43,7 +43,7 @@ We only accept extensions under OSL-3 or MIT licenses.
 Adding an Extension
 -------------------
 
-To be able to add an extension you have to be logged in to tho OroCRM Extensions Store website. The Add Extension page
+To be able to add an extension you have to be logged in to the Oro Extensions Store website. The Add Extension page
 can be reached via the user menu in the top right corner of the page or via link on the My Marketplace page.
 
 First thing you have to do is to choose an extension type: paid or free.
 
@@ -1,7 +1,7 @@
-:title: Bundles and Extensions Management in OroCommerce, OroCRM, OroPlatform
+:title: Bundles and Extensions Management in Oro Application
 
 .. meta::
-   :description: Bundles and extensions management guides for the OroCommerce, OroCRM, OroPlatform backend developers
+   :description: Bundles and extensions management guides for the Oro Application backend developers
 
 .. _dev-guide-bundles-extensions:
 
 
@@ -1,7 +1,7 @@
 :title: Enabling and Disabling Oro Application Features
 
 .. meta::
-   :description: Practical guides on enabling and disabling application features via the system configuration UI in the OroCommerce, OroCRM, and OroPlatform backend
+   :description: Practical guides on enabling and disabling application features via the system configuration UI in the Oro application backend
 
 .. _dev-feature-toggle:
 
 
@@ -79,7 +79,6 @@ Backend Developer Guide is an essential resource for developers that provides co
       <li><a class="" href="system-configuration/">System Configuration</a></li>
       <li><a class="tag-very-important" href="configuration/">Configuration Reference</a></li>
       <li><a class="" href="automated-tests/">Automated Tests</a></li>
-      <li><a class="" href="extend-crm/">Extending OroCRM</a></li>
       <li><a class="tag-important" href="extend-commerce/">Extending OroCommerce</a></li>
       <li><a class="tag-very-important" href="api/">API Developer Guide</a></li>
       <li><a class="" href="organization-types/">Organization Types</a></li>
@@ -115,7 +114,6 @@ Backend Developer Guide is an essential resource for developers that provides co
    logging/index
    system-configuration/index
    configuration/index
-   extend-crm/index
    extend-commerce/index
    third-party-extensions/index
    automated-tests/index
 
@@ -1,4 +1,4 @@
-:title: Logging Concept and Strategy in OroCommerce, OroCRM, OroPlatform
+:title: Logging Concept and Strategy in Oro Application
 
 .. meta::
     :description: An overview of the logging concept, strategy, and standards
 
@@ -1,4 +1,4 @@
-:title: Message Queue Concepts in OroCommerce, OroCRM, OroPlatform
+:title: Message Queue Concepts in Oro Application
 
 .. meta::
    :description: Message queue concept and architecture guides
 
@@ -1,4 +1,4 @@
-:title: Backend Navigation Customization of OroCommerce, OroCRM, OroPlatform
+:title: Backend Navigation Customization of Oro Application
 
 .. meta::
    :description: Menus, breadcrumbs, and titles customization manual for the backend developers
@@ -12,7 +12,7 @@ Navigation
 Menus
 -----
 
-The OroPlatform and the OroCRM come with a rich user interface. You can access every application part by browsing the provided navigation items.
+Oro Applications come with a rich user interface. You can access every application part by browsing the provided navigation items.
 
 OroPlatform leverages the famous |KnpMenuBundle| to provide highly customizable menus. You can add your own menu items to access your project-specific interfaces or even replace existing items.
 
 
@@ -1,7 +1,7 @@
 :title: Configure Restrictions and Limitations for Organizations
 
 .. meta::
-   :description: A guide on how to add and configure organization types to provide a set of restrictions and limitations for organizations in the Enterprise editions of OroCommerce, OroCRM, and OroPlatform.
+   :description: A guide on how to add and configure organization types to provide a set of restrictions and limitations for organizations in the Enterprise editions of Oro applications.
 
 .. _dev-organization-types:
 
 
@@ -1,4 +1,4 @@
-:title: Scopes Configuration in OroCommerce, OroCRM, OroPlatform
+:title: Scopes Configuration in Oro Application
 
 .. meta::
    :description: Introduction to the Oro scope entity and its configuration settings with examples
 
@@ -1,4 +1,4 @@
-:title: Security Capabilities in OroCommerce, OroCRM, OroPlatform
+:title: Security Capabilities in Oro Application
 
 .. meta::
    :description: Guidance on security settings and access levels configuration for the backend developers
Original file line number	Diff line number	Diff line change
`@@ -1,5 +1,3 @@`
`1`		`-:oro_documentation_types: OroCommerce`
`2`		`-`
`3`	`1`	`.. _web-api--storefront-routes:`
`4`	`2`
`5`	`3`	`Storefront Routes`
Original file line number	Diff line number	Diff line change
`@@ -1,5 +1,3 @@`
`1`		`-:oro_documentation_types: OroCommerce`
`2`		`-`
`3`	`1`	`.. _web-api--storefront:`
`4`	`2`
`5`	`3`	`Storefront REST API`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-:title: Cron Setup and Configuration in OroCommerce, OroCRM, OroPlatform`
	`1`	`+:title: Cron Setup and Configuration in Oro Applications`
`2`	`2`
`3`	`3`	`.. meta::`
`4`	`4`	`:description: Instructions on the time-based cron jobs setup and configuration in the Oro applications for the backend developers`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-:title: Backend Emails Configuration in OroCommerce, OroCRM, OroPlatform`
	`1`	`+:title: Backend Emails Configuration in Oro Application`
`2`	`2`
`3`	`3`	`.. meta::`
`4`	`4`	`:description: Emails and templates configuration manuals for the backend developers`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-:title: Entities Data Management in OroCommerce, OroCRM, OroPlatform`
	`1`	`+:title: Entities Data Management in Oro Application`
`2`	`2`
`3`	`3`	`.. meta::`
`4`	`4`	`:description: Entities data management guides for the backend developers`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-:title: Entities Management in OroCommerce, OroCRM, OroPlatform`
	`1`	`+:title: Entities Management in Oro Application`
`2`	`2`
`3`	`3`	`.. meta::`
`4`	`4`	`:description: A step by step tutorial for entities management in the Oro applications for the backend developers`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-:title: Logging Concept and Strategy in OroCommerce, OroCRM, OroPlatform`
	`1`	`+:title: Logging Concept and Strategy in Oro Application`
`2`	`2`
`3`	`3`	`.. meta::`
`4`	`4`	`:description: An overview of the logging concept, strategy, and standards`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-:title: Message Queue Concepts in OroCommerce, OroCRM, OroPlatform`
	`1`	`+:title: Message Queue Concepts in Oro Application`
`2`	`2`
`3`	`3`	`.. meta::`
`4`	`4`	`:description: Message queue concept and architecture guides`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-:title: Scopes Configuration in OroCommerce, OroCRM, OroPlatform`
	`1`	`+:title: Scopes Configuration in Oro Application`
`2`	`2`
`3`	`3`	`.. meta::`
`4`	`4`	`:description: Introduction to the Oro scope entity and its configuration settings with examples`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-:title: Security Capabilities in OroCommerce, OroCRM, OroPlatform`
	`1`	`+:title: Security Capabilities in Oro Application`
`2`	`2`
`3`	`3`	`.. meta::`
`4`	`4`	`:description: Guidance on security settings and access levels configuration for the backend developers`