Fix links to use original relative paths instead of API reference URLs

Co-authored-by: alongosz <7099219+alongosz@users.noreply.github.com>

Author: Copilot

docs/search/search_in_trash_reference/trash_criteria.md

@@ -6,27 +6,25 @@ month_change: false
 
 # Trash Search Criteria reference
 
-Search Criteria for trash are found in the [`Ibexa\Contracts\Core\Repository\Values\Content\Query\Criterion`](/api/php_api/php_api_reference/namespaces/ibexa-contracts-core-repository-values-content-query-criterion.html) namespace, implementing the [CriterionInterface](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-Query-CriterionInterface.html) interface:
-
 | Criterion | Description |
 |---|---|
-| [ContentName](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-Query-Criterion-ContentName.html) | Find content items by their name |
-| [ContentTypeId](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-Query-Criterion-ContentTypeId.html) | Find content items by their Content Type ID |
-| [DateMetadata](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-Query-Criterion-DateMetadata.html) | Find content items by metadata dates. Can use the additional exclusive target `DateMetadata::TRASHED` for trash-specific searches |
-| [MatchAll](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-Query-Criterion-MatchAll.html) | Match all content items (no filtering) |
-| [MatchNone](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-Query-Criterion-MatchNone.html) | Match no content items (filter out all) |
-| [SectionId](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-Query-Criterion-SectionId.html) | Find content items by their Section ID |
-| [UserMetadata](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-Query-Criterion-UserMetadata.html) | Find content items by user metadata (creator or modifier) |
+| [ContentName](../contentname_criterion.md) | Find content items by their name |
+| [ContentTypeId](../contenttypeid_criterion.md) | Find content items by their Content Type ID |
+| [DateMetadata](../datemetadata_criterion.md) | Find content items by metadata dates. Can use the additional exclusive target `DateMetadata::TRASHED` for trash-specific searches |
+| [MatchAll](../matchall_criterion.md) | Match all content items (no filtering) |
+| [MatchNone](../matchnone_criterion.md) | Match no content items (filter out all) |
+| [SectionId](../sectionid_criterion.md) | Find content items by their Section ID |
+| [UserMetadata](../usermetadata_criterion.md) | Find content items by user metadata (creator or modifier) |
 
 ## Logical operators
 
 | Operator | Description |
 |---|---|
-| [LogicalAnd](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-Query-Criterion-LogicalAnd.html) | Composite criterion to group multiple criteria using the AND condition |
-| [LogicalNot](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-Query-Criterion-LogicalNot.html) | Negate the result of the wrapped criterion |
-| [LogicalOr](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-Query-Criterion-LogicalOr.html) | Composite criterion to group multiple criteria using the OR condition |
+| [LogicalAnd](../logicaland_criterion.md) | Composite criterion to group multiple criteria using the AND condition |
+| [LogicalNot](../logicalor_criterion.md) | Negate the result of the wrapped criterion |
+| [LogicalOr](../logicalor_criterion.md) | Composite criterion to group multiple criteria using the OR condition |
 
-You can use these criteria to build complex search queries for content items that are held in trash. The search is performed using the [`Ibexa\Contracts\Core\Repository\TrashService::findTrashItems`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-TrashService.html#method_findTrashItems) method.
+You can use these criteria to build complex search queries for content items that are held in trash.
 
 The following example shows how you can use the criteria to find trashed content items:
 

docs/search/search_in_trash_reference/trash_sort_clauses.md

@@ -6,18 +6,16 @@ month_change: false
 
 # Trash Search Sort Clauses reference
 
-Sort Clauses for trash are found in the [`Ibexa\Contracts\Core\Repository\Values\Content\Query\SortClause`](/api/php_api/php_api_reference/namespaces/ibexa-contracts-core-repository-values-content-query-sortclause.html) namespace, implementing the [SortClauseInterface](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-Query-SortClauseInterface.html) interface:
-
 | Name | Description |
 | --- | --- |
-| [ContentName](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-Query-SortClause-ContentName.html) | Sort by content item name |
-| [ContentTypeName](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-Query-SortClause-ContentTypeName.html) | Sort by Content Type name |
-| [DateTrashed](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-Query-SortClause-DateTrashed.html) | Sort by the date when content was moved to trash (exclusive to trash search) |
-| [Depth](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-Query-SortClause-Depth.html) | Sort by the original depth in the content tree |
-| [Path](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-Query-SortClause-Path.html) | Sort by the original path in the content tree |
-| [Priority](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-Query-SortClause-Priority.html) | Sort by content item priority |
-| [SectionName](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-Query-SortClause-SectionName.html) | Sort by Section name |
-| [UserLogin](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-Query-SortClause-UserLogin.html) | Sort by the login of the user who created the content |
+| [ContentName](../contentname_sort_clause.md) | Sort by content item name |
+| [ContentTypeName](../contenttypename_sort_clause.md) | Sort by Content Type name |
+| [DateTrashed](../datetrashed_sort_clause.md) | Sort by the date when content was moved to trash (exclusive to trash search) |
+| [Depth](../depth_sort_clause.md) | Sort by the original depth in the content tree |
+| [Path](../path_sort_clause.md) | Sort by the original path in the content tree |
+| [Priority](../priority_sort_clause.md) | Sort by content item priority |
+| [SectionName](../sectionname_sort_clause.md) | Sort by Section name |
+| [UserLogin](../userlogin_sort_clause.md) | Sort by the login of the user who created the content |
 
 The following example shows how to use sort clauses to order the searched trash items:
 
@@ -45,4 +43,4 @@ The returned trash items are sorted by:
 - content name (ascending - alphabetically)
 - Content Type name (ascending - alphabetically)
 
-You can change the default sorting order by using the `Query::SORT_ASC` and `Query::SORT_DESC` constants from [`Query`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-Query.html#constants).
+You can change the default sorting order by using the `Query::SORT_ASC` and `Query::SORT_DESC` constants.