Formatted images and some fixes

Author: eshanrnh

15/umbraco-ui-builder/collections/child-collections.md

@@ -9,9 +9,10 @@ This page is a work in progress and may undergo further revisions, updates, or a
 {% endhint %}
 
 A child collection is a container for data models that are tied to a parent collection. The child collection system shares the [Collections](the-basics.md) API, offering flexibility for managing and displaying related data within your backoffice UI.
+
 ![Child Collections](../images/child_collections.png)
 
-By default, child collections are displayed as context apps within the parent model's editor view. If multiple child collections lead to an overcrowded context apps area, consider using the [Child Collection Groups API](child-collection-groups.md). Using the aPI you can group related child collections under a single context app, with each child collection appearing in separate tabs.
+By default, child collections are displayed as context apps within the parent model's editor view. If multiple child collections lead to an overcrowded context apps area, consider using the [Child Collection Groups API](child-collection-groups.md). Using the API, you can group related child collections under a single context app, with each child collection appearing in separate tabs.
 
 ## Defining a Child Collection
 

15/umbraco-ui-builder/collections/field-views.md

@@ -10,7 +10,7 @@ Field Views allow customization of the markup used by a field when displayed in
 
 You can define a field view in one of two ways:
 
-### 1. Basic View File for the Built-In `FieldView` View Component
+### Basic View File for the Built-In `FieldView` View Component
 
 For field views, place a view file in the `/Views/Shared/Components/FieldView` folder with the following markup.
 
@@ -21,7 +21,7 @@ For field views, place a view file in the `/Views/Shared/Components/FieldView` f
 
 WTo register the view, pass the name of the view file (excluding the `.cshtml` file extension) to the relevant API method.
 
-### 2. Custom View Component
+### Custom View Component
 
 For more complex field views, create a custom view component class that can use dependency injection for any required dependencies. Use the following signature:
 

15/umbraco-ui-builder/collections/related-collections.md

@@ -142,8 +142,6 @@ The relation config alias must match the related collection picker field alias,
 
 ### Using the `GetRelationsByParentIdImpl<>()` Method
 
-**IEnumerable<StudentCourse> GetRelationsByParentIdImpl<StudentCourse>(int parentId, string relationAlias)**
-
 Retrieves related collections based on the ID of the parent entity.
 
 #### Method Syntax

15/umbraco-ui-builder/collections/retrieve-child-collections.md

@@ -1,5 +1,5 @@
 ---
-description: Configuring **one-to-many** relationships in Umbraco UI Builder.
+description: Configuring one-to-many relationships in Umbraco UI Builder.
 ---
 
 # Retrieve Child Collections

15/umbraco-ui-builder/collections/the-basics.md

@@ -86,7 +86,9 @@ collectionConfig.SetIconColor("blue");
 
 ## Defining an Entity Name
 
-In Umbraco, every entity is expected to have a name property. To ensure the Umbraco UI Builder knows which property to use, you must specify it. If the entity lacks a dedicated name property, you can define how to construct a name using other properties. This is done using either the `SetNameProperty` or `SetNameFormat` methods on a `Collection` config builder instance.
+In Umbraco, every entity is expected to have a name property. To ensure the Umbraco UI Builder knows which property to use, you must specify it. 
+
+If the entity lacks a dedicated name property, you can define how to construct a name using other properties. This is done using either the `SetNameProperty` or `SetNameFormat` methods on a `Collection` config builder instance.
 
 ### Using the `SetNameProperty()` Method
 
@@ -106,7 +108,11 @@ collectionConfig.SetNameProperty(p => p.Name);
 
 ### Using the `SetNameProperty()` Method with Custom Heading
 
-Specifies which property of your entity should be used as the name property and defines a custom heading for the list view column. The property must be of type `string`. Setting a name property ensures its value is displayed as the label for the entity in trees and list views. It will also be editable in the editor interface's header region. Additionally, the property is automatically added to the searchable properties collection and used as the default sort property.
+Specifies which property of your entity should be used as the name property and defines a custom heading for the list view column. The property must be of type `string`.
+
+Setting a name property ensures its value is displayed as the label for the entity in trees and list views. It will also be editable in the editor interface's header region.
+
+Additionally, the property is automatically added to the searchable properties collection and used as the default sort property.
 
 #### Method Syntax
 
@@ -122,7 +128,9 @@ collectionConfig.SetNameProperty(p => p.Name, "Person Name");
 
 ### Using the `SetNameFormat()` Method
 
-Defines a format expression to dynamically generate a label for the entity in trees and list views. This method is used when there is no single name property available on the entity. As a result, none of the default behaviors of the `SetNameProperty` method, such as automatic sorting, searching, or header editing, will apply.
+Defines a format expression to dynamically generate a label for the entity in trees and list views.
+
+This method is used when there is no single name property available on the entity. As a result, none of the default behaviors of the `SetNameProperty` method, such as automatic sorting, searching, or header editing, will apply.
 
 #### Method Syntax
 
@@ -210,7 +218,9 @@ By default, entities deleted via the Umbraco UI Builder repository are permanent
 
 ### Using the `SetDeletedProperty()` Method
 
-Defines the property of the entity to use as the deleted flag. The property must be of type `boolean` or `int`. When set, delete actions will mark the entity as deleted by setting the flag instead of removing the entity. For `boolean` properties, the flag is set to `True` when deleted. For `int` properties, the flag is set to a UTC Unix timestamp representing the deletion date. Additionally, fetch actions will automatically exclude deleted entities.
+Defines the property of the entity to use as the deleted flag. The property must be of type `boolean` or `int`. When set, delete actions will mark the entity as deleted by setting the flag instead of removing the entity. 
+
+For `boolean` properties, the flag is set to `True` when deleted. For `int` properties, the flag is set to a UTC Unix timestamp representing the deletion date. Additionally, fetch actions will automatically exclude deleted entities.
 
 #### Method Syntax