docs(documentation): Update project documentation based on feedback

Author: RandomByte

packages/documentation/docs/pages/Project.md

@@ -16,20 +16,28 @@ Also see [UI5 Project: Configuration](./Configuration.md#general-configuration)
 
 > **Note:** The term `component` as used in the UI5 CLI project type differs from the `sap.app/type` property in the `manifest.json` file at runtime. In most cases, a CLI project of type `component` is still a runtime "application". For details on the `sap.app/type` property in `manifest.json`, refer to the [manifest documentation](https://ui5.sap.com/#/topic/be0cf40f61184b358b5faedaec98b2da.html#loiobe0cf40f61184b358b5faedaec98b2da/section_sap_app).
 
-Projects of the `component` type are typical component-like UI5 applications. They usually run in a container-like root application, such as the SAP Fiori launchpad (FLP) sandbox, alongside other UI5 applications.
+Projects of the `component` type cover a range of use cases beyond typical standalone UI5 applications:
+
+- **Application components:** These are typical UI5 applications, designed to run in container-like application such as the SAP Fiori launchpad (FLP). These generally inherit from `sap.ui.core.UIComponent` (or a subclass) and define the `manifest.json` property `sap.app/type: application`.
+- **Reusable UI components:** Provide UI elements or features that can be embedded in different contexts. These typically inherit from `sap.ui.core.UIComponent` and define the `manifest.json` property `sap.app/type: component`.
+- **Faceless components:** Provide functionality without a user interface. These are defined with `manifest.json` property `sap.app/type: component` and inherit from `sap.ui.core.Component` (not `UIComponent`).
+
+Please also refer to the [components documentation](https://ui5.sap.com/#/topic/958ead51e2e94ab8bcdc90fb7e9d53d0) for more details.
 
 To allow multiple component projects to coexist in the same environment, each project is served under its own namespace, for example `/resources/my/bookstore/admin`. In contrast, `application`-type projects act as root projects and are served at `/`, without a namespace.
 
-By default, component projects use the same directory structure as library projects: they include `src` and `test` directories in the root. The integrated server uses both directories. However, when you build the project, the `test` directory is ignored because it shouldn't be deployed to production environments. Both directories can have either a flat or a namespace structure. If you use a flat structure, the project namespace derives from the `"sap.app".id` property in the `manifest.json`.
+By default, component projects use the same directory structure as library projects: they include `src` and `test` directories in the root. Both directories can have either a flat or a namespace structure. If you use a flat structure, the project namespace derives from the `"sap.app".id` property in the `manifest.json`.
 
 A component project must contain both, a `Component.js` and a `manifest.json` file.
 
 Unlike `application`-type projects, component projects typically don't have dedicated `index.html` files in their regular resources (`src/`). However, you can still run them standalone. You can do this by using a dedicated HTML file located in their test resources or by declaring a development dependency to an application-type project that can serve the component, such as the FLP sandbox.
 
-Component projects support all [output styles](./CLI.md#ui5-build) that library projects currently support. This allows a deployment where you can omit the namespace from the final directory structure using the output style: `flat`.
+Component projects support all [output styles](#build-output-style) that library projects currently support. This allows a deployment where you can omit the namespace from the final directory structure using the output style: `flat`.
+
+For more details, see also [RFC 0018 Component Type](https://github.com/UI5/cli/blob/rfc-component-type/rfcs/0018-component-type.md#rfc-0018-component-type).
 
 ### application
-Projects of the `application` type typically serve as the main or root project. In a project's dependency tree, there should be only one project of this type. If the system detects additional application projects, it ignores those that are further away from the root.
+Projects of the `application` type typically serve as the main or root project. In a project's dependency tree, there shouldn't be more than one project of this type. If the system detects additional application projects, it ignores those that are further away from the root.
 
 The source directory of an application (typically named `webapp`) is mapped to the virtual root path `/`.
 
@@ -61,32 +69,27 @@ The _Output Style_ offers you control over your project's build output folder. N
 
 In the table below you can find the available combinations of project type & output style.
 
-| Project Type / Requested Output Style | Resulting Style |
-|---|---|
-| **application** | |
-| `Default` | Root project is written `Flat`-style. ^1^ |
-| `Flat` | Same as `Default`. |
-| `Namespace` | Root project is written `Namespace`-style (resources are prefixed with the project's namespace). ^1^ |
-| **component** | |
-| `Default` | Root project is written `Namespace`-style. ^1^ |
-| `Flat` | Root project is written `Flat`-style (without its namespace, logging warnings for resources outside of it). ^1^ |
-| `Namespace` | Same as `Default`. |
-| **library** | |
-| `Default` | Root project is written `Namespace`-style. ^1^ |
-| `Flat` | Root project is written `Flat`-style (without its namespace, logging warnings for resources outside of it). ^1^ |
-| `Namespace` | Same as `Default`. |
-| **theme-library** | |
-| `Default` | Root project is written in the style of the sources (multiple namespaces). ^1^ |
-| `Flat` | **Unsupported** ^2^ |
-| `Namespace` | **Unsupported** ^2^ |
-| **module** | |
-| `Default` | Root project is written with the [configured paths](https://ui5.github.io/cli/v5/pages/Configuration/#available-path-mappings). ^1^ |
-| `Flat` | **Unsupported** ^3^  |
-| `Namespace` | **Unsupported**  ^3^ |
-
-^1^ The Output Style is only applied to the root project's output folder structure. Any dependencies included in the build would retain their `Default` output style.  
-^2^ Theme libraries in most cases have more than one namespace.  
-^3^ Modules have explicit path mappings configured and no namespace concept.  
+| Project Type | Requested Output Style | Resulting Style |
+| :--- | :--- | :--- |
+| **component** | `Default` | Root project is written `Namespace`-style.¹ |
+| | `Flat` | Root project is written `Flat`-style (without its namespace, logging warnings for resources outside of it).¹ |
+| | `Namespace` | Same as `Default`. |
+| **application** | `Default` | Root project is written `Flat`-style.¹ |
+| | `Flat` | Same as `Default`. |
+| | `Namespace` | Root project is written `Namespace`-style (resources are prefixed with the project's namespace).¹ |
+| **library** | `Default` | Root project is written `Namespace`-style.¹ |
+| | `Flat` | Root project is written `Flat`-style (without its namespace, logging warnings for resources outside of it).¹ |
+| | `Namespace` | Same as `Default`. |
+| **theme-library** | `Default` | Root project is written in the style of the sources (multiple namespaces).¹ |
+| | `Flat` | **Unsupported** ² |
+| | `Namespace` | **Unsupported** ² |
+| **module** | `Default` | Root project is written with the [configured paths](https://ui5.github.io/cli/v5/pages/Configuration/#available-path-mappings).¹ |
+| | `Flat` | **Unsupported** ³ |
+| | `Namespace` | **Unsupported** ³ |
+
+¹ The Output Style is only applied to the root project's output folder structure. Any dependencies included in the build would retain their `Default` output style.  
+² Theme libraries in most cases have more than one namespace.  
+³ Modules have explicit path mappings configured and no namespace concept.  
 
 
 <div style="margin: 1rem 0;">