DOC-2096: Remove CRM mentions and (DOC-2097) the :scale: image parameter from documentation (#36465)

Author: DariaHanzenko

api/index.rst

@@ -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

backend/api/storefront-routes.rst

@@ -1,5 +1,3 @@
-:oro_documentation_types: OroCommerce
-
 .. _web-api--storefront-routes:
 
 Storefront Routes

backend/api/storefront.rst

@@ -1,5 +1,3 @@
-:oro_documentation_types: OroCommerce
-
 .. _web-api--storefront:
 
 Storefront REST API

backend/architecture/custom-application.rst

@@ -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

backend/architecture/customization/index.rst

@@ -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.
 

backend/architecture/differences.rst

@@ -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.

backend/architecture/framework/index.rst

@@ -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::

backend/architecture/index.rst

@@ -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:
 

backend/architecture/structure/index.rst

@@ -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.
 

backend/automated-tests/debug-behat-tests.rst

@@ -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