IBX-4175: Update/Fix several internal and external links (#2117)

Author: adriendupuis

docs/administration/admin_panel/roles_admin_panel.md

@@ -24,7 +24,7 @@ See [example use case](permission_use_cases.md#restrict-editing-to-part-of-the-t
 
     Limitation specifies what a User can do, not what they can't do.
     A `Location` Limitation, for example, gives the User access to content with a specific Location, 
-    not prohibits it. See [Available Limitations](limitations.md#available-limitations) for further information.
+    not prohibits it. See [Limitation reference](limitation_reference.md) for further information.
 
 **Assignments**
 

docs/administration/admin_panel/system_information_admin_panel.md

@@ -4,7 +4,7 @@ description: System information provides basic system information such as versio
 
 # System Information
 
-The System Information panel in the Back Office is sourced in the [`ibexa/support-tools` repository](https://github.com/ibexa/support-tools).
+The System Information panel in the Back Office is sourced in the [`ibexa/system-info` repository](https://github.com/ibexa/system-info).
 There you will also find basic system information such as versions of all installed packages.
 
 ![System Information](admin_panel_system_info.png "System Information")

docs/administration/back_office/back_office_elements/importing_assets_from_bundle.md

@@ -78,7 +78,7 @@ module.exports = (IbexaConfig, IbexaConfigManager) => {
     After you add new files, run `php bin/console cache:clear`.
 
     For a full example of overriding configuration,
-    see [`ibexa.config.manager.js`](https://github.com/ibexa/matrix-fieldtype/blob/main/src/bundle/Resources/encore/ibexa.config.manager.js).
+    see [`ibexa.config.manager.js`](https://github.com/ibexa/fieldtype-matrix/blob/main/src/bundle/Resources/encore/ibexa.config.manager.js).
 
 To add a new configuration under your own namespace and with its own dependencies, 
 create an `ibexa.webpack.custom.config.js` file that you create either in the bundle's `Resources/encore/` folder, 

docs/administration/back_office/back_office_menus/back_office_menus.md

@@ -9,7 +9,7 @@ Back Office menus are based on the [KnpMenuBundle](https://github.com/KnpLabs/Kn
 !!! tip
 
     For general information on how to use `MenuBuilder`,
-    see [the official KnpMenuBundle documentation](https://symfony.com/doc/current/bundles/KnpMenuBundle/index.html).
+    see [the official KnpMenuBundle documentation](https://symfony.com/bundles/KnpMenuBundle/current/index.html).
 
 Menus are extensible using event subscribers, for example:
 

docs/administration/back_office/browser/browser.md

@@ -185,4 +185,4 @@ class JohnDoeCanSelectMore implements EventSubscriberInterface
 }
 ```
 
-For more information, see [Symfony Doctrine Event Listeners and Subscribers tutorial.]([[= symfony_doc =]]/event_dispatcher.html#creating-an-event-subscriber)
+For more information, see [Symfony Doctrine Event Listeners and Subscribers tutorial]([[= symfony_doc =]]/event_dispatcher.html#creating-an-event-subscriber).

docs/administration/back_office/content_type_anchor_menu.md

@@ -5,7 +5,7 @@ description: Add anchor menu to the Content Type configuration screen, to make F
 # Add anchor menu to Content Type edit screen
 
 With the anchor menu you can increase visibility of certain [Field Types](field_types.md), which provide more complex functionality, 
-by separating them from the [Field definitions](content_model.md#field-definitions) section in [Content Type](content_model.md#content-types) configuration screen. 
+by separating them from the [Field definitions](content_types.md#field-definitions) section in [Content Type](content_types.md) configuration screen. 
 One example of such Field Type would be [SEO]([[= user_doc =]]/search_engine_optimization/work_with_seo/), 
 because it handles functionality that applies to all Content items of the Content Type.
 You can use the anchor menu feature with other Field Types, including [custom ones](create_custom_generic_field_type.md).

docs/administration/configuration/configuration.md

@@ -50,7 +50,7 @@ Internally and by convention, keys follow a *dot syntax*, where the different se
 Keys are usually prefixed by a *namespace* corresponding to your application. All kinds of values are accepted, including arrays and deep hashes.
 
 For configuration that is meant to be exposed to an end-user (or end-developer),
-it's usually a good idea to also [implement semantic configuration.]([[= symfony_doc =]]/components/config/definition.html)
+it's usually a good idea to also [implement semantic configuration]([[= symfony_doc =]]/components/config/definition.html).
 
 Note that you can also [implement SiteAccess-aware semantic configuration](siteaccess_aware_configuration.md).
 

docs/administration/configuration/repository_configuration.md

@@ -26,9 +26,9 @@ ibexa:
 
     Legacy storage engine is the default storage engine for the Repository.
 
-    It uses [Doctrine DBAL](http://docs.doctrine-project.org/projects/doctrine-dbal/en/latest/) (Database Abstraction Layer).
+    It uses [Doctrine DBAL](https://www.doctrine-project.org/projects/doctrine-dbal/en/latest/) (Database Abstraction Layer).
     Database settings are supplied by [DoctrineBundle](https://github.com/doctrine/DoctrineBundle).
-    As such, you can refer to [DoctrineBundle's documentation](https://github.com/doctrine/DoctrineBundle/blob/master/Resources/doc/configuration.rst#doctrine-dbal-configuration).
+    As such, you can refer to [DoctrineBundle's documentation](https://github.com/doctrine/DoctrineBundle/blob/2.7.x/Resources/doc/configuration.rst#doctrine-dbal-configuration).
 
 If no Repository is specified for a SiteAccess or SiteAccess group,
 the first Repository defined under `ibexa.repositories` will be used:

docs/administration/content_organization/content_types.md

@@ -17,7 +17,7 @@ Content Types are organized into groups.
 
 You can add your own groups here to keep your Content Types in better order.
 
-For a full tutorial, see [Create a Content Type](first_steps.md#create-a-content-type) or follow [user documentation](https://doc.ibexa.co/projects/userguide/en/latest/organizing_the_site/#content-types).
+For a full tutorial, see [Add a Content Type](first_steps.md#add-a-content-type) or follow [user documentation](https://doc.ibexa.co/projects/userguide/en/latest/content_management/create_edit_content_types/).
 For a detailed overview of the content model, see [Content model overview](content_model.md).
 
 ## Content Type metadata

docs/administration/content_organization/object_states.md

@@ -19,5 +19,5 @@ By default, [[= product_name =]] contains one Object state group: **Lock**, with
 
 ![**Lock** Object state](object_state_lock.png "Lock Object state")
 
-Object states can be used in conjunction with [permissions](permission_overview.md), in particular with the [State Limitation](limitation_reference.md#state-limitation).
+Object states can be used in conjunction with [permissions](permission_overview.md), in particular with the [Object State Limitation](limitation_reference.md#object-state-limitation).
 Their specific use cases depend on your needs and the setup of your permission system.