Updated EN links

content/8.x/admin/administration-panel/Administration-Panel.adoc

@@ -68,7 +68,7 @@ image:Admin-Panel-Bottom.png[Admin-Panel-Bottom.png]
 * link:../../../../admin/administration-panel/developer-tools/#_display_modules_and_subpanels[Display Modules and Subpanels]
 ** Display Modules and Subpanels
 
-* link:../../../../admin/administration-panel/developer-tools/#_history_subpanel[Hisotry Subpanel]
+* link:../../../../admin/administration-panel/developer-tools/#_history_subpanel[History Subpanel]
 ** History Subpanel
 
 * link:../../../../admin/administration-panel/advanced-openadmin/#_aos_settings[Sales Module Settings]
@@ -94,36 +94,36 @@ image:Admin-Panel-Bottom.png[Admin-Panel-Bottom.png]
 
 ==== Admin Tools
 
-* link:../../../admin/administration-panel/system[System]
+* link:../../../../admin/administration-panel/system/[System]
 ** Repair
 ** Backups
 ** Diagnostic Tool
 
-* link:../../../user/introduction/user-interface/record-management/#_importing_records[Importing Records]
+* link:../../../../user/introduction/user-interface/record-management/#_importing_records[Importing Records]
 ** Import Wizard
 
-* link:../../../admin/administration-panel/developer-tools/#_module_loader[Module Loader]
+* link:../../../../admin/administration-panel/developer-tools/#_module_loader[Module Loader]
 ** Module Loader
 
 ==== Developer Tools
 
-* link:../../../admin/administration-panel/studio[Studio]
+* link:../../../../admin/administration-panel/studio[Studio]
 ** Studio
 
-* link:../../../admin/administration-panel/developer-tools/#_rename_modules[Developer Tools]
+* link:../../../../admin/administration-panel/developer-tools[Developer Tools]
 ** Rename Modules
 ** Module Builder
 ** Dropdown Editor
 
-* link:../../../user/advanced-modules/workflow[Workflows]
+* link:../../../../user/advanced-modules/workflow[Workflows]
 ** Workflow Manager
 
 ==== Google Suite
 
-* link:../../../admin/administration-panel/google-sync/#_overview[Google Credentials and Syncing]
+* link:../../../../admin/administration-panel/google-sync/#_overview[Google Credentials and Syncing]
 ** Google Calendar Settings
 
-* link:../../../admin/administration-panel/google-maps/#_google_map_setup[Google Maps]
+* link:../../../../admin/administration-panel/google-maps/#_google_map_setup[Google Maps]
 ** Google Maps Settings
 ** Geocoding Test
 ** Geocode Addresses

content/8.x/admin/configuration/Sessions-Configuration.adoc

@@ -7,7 +7,7 @@ weight: 30
 
 == Option 1. Changing session dir in php.ini
 
-It is possible to update the global session dir by changing php's link:session.save-path[https://www.php.net/manual/en/session.configuration.php#ini.session.save-path] directive on your php.ini file.
+It is possible to update the global session dir by changing php's link:https://www.php.net/manual/en/session.configuration.php#ini.session.save-path[session.save_path] directive on your php.ini file.
 
 
 == Option 2. Changing session dir in SuiteCRM configuration

content/8.x/admin/releases/8.5/_index.en.adoc

@@ -76,7 +76,7 @@ If you want to get involved and submit a fix, fork the repo and when ready pleas
 
 Please link:https://suitecrm.com/suitecrm-pre-release/[visit the official website] to find the appropriate upgrade package.
 
-To report any security issues please follow our link:../../../community/security-policy[Security Policy] and send them directly to us via email [email protected]
+To report any security issues please follow our link:../../../../community/security-policy[Security Policy] and send them directly to us via email [email protected]
 
 '''
 
@@ -102,7 +102,7 @@ Angular version has been updated to v16. For development purposes you will need
 
 With the upgrade to angular v16 the version of the `@angular-architects/module-federation` lib has also been updated.
 
-Previously built extensions will need to be updated. Please read the link:../../../developer/extensions/frontend/migration/8.5[Frontend extension - Migrate to SuiteCRM 8.5+] guide for information on how to upgrade.
+Previously built extensions will need to be updated. Please read the link:../../../developer/extensions/frontend/migration/migration-8.5/[Frontend extension - Migrate to SuiteCRM 8.5+] guide for information on how to upgrade.
 
 
 ==== icon:star[] Enhancements

content/8.x/developer/extensions/backend/process-api/process-handler.en.adoc

@@ -43,7 +43,7 @@ As a best practice extension backend code should be added to `extensions/<your-e
 . Within that folder create the `CaseCalculatePriority.php`, i.e. `extensions/defaultExt/modules/Cases/Service/Fields/CaseCalculatePriority.php`
 .. If you are not using the recommended path, make sure that the `namespace` follows the one you are using
 .. On our example the namespace is `namespace App\Extension\defaultExt\modules\Cases\Service\Fields;`
-. On `CaseCalculatePriority.php`, add the code on the snippet on link:./#_3_2_process_handler_implementation[3.2 Process handler implementation] section
+. On `CaseCalculatePriority.php`, add the code on the snippet on link:./#_2_2_process_handler_implementation[2.2 Process handler implementation] section
 . Run `php bin/console cache:clear` or delete the contents of the cache folder under the root of the project
 . Re-set the correct file permissions if you need to (This will depend on your setup and the user you are using to make changes)
 

content/8.x/developer/extensions/frontend/logic/action-logic/fe-extensions-display-action-logic.adoc

@@ -158,4 +158,4 @@ employees is greater than 5 and less than 100 then your code should look somethi
                     ],
 ----
 
-For more information on operators see link:../operators/_index.en.adoc[here.]
+For more information on operators see link:../../operators/[here.]

content/8.x/developer/extensions/frontend/migration/8.5/_index.en.adoc → content/8.x/developer/extensions/frontend/migration/Migration-8.5.adoc

@@ -6,7 +6,7 @@ weight: 10
 :imagesdir: /images/en/8.x/developer/extensions/front-end/migration
 
 {{% notice info %}}
-The following documentation is for SuiteCRM Version 8+; to see documentation for Version 7, click link:../../../../../developer/introduction[here].
+The following documentation is for SuiteCRM Version 8+; to see documentation for Version 7, click link:../../../../../../developer/introduction[here].
 {{% /notice %}}
 
 

content/admin/administration-panel/Developer Tools.adoc

@@ -12,24 +12,24 @@ weight: 50
 == Studio
 
 The Studio tools allow you to customise the information shown in the
-modules and how it is displayed. 
+modules and how it is displayed.
 
 See the dedicated link:../studio[Studio guide] for more
 information on how to use the Studio tools.
 
 == Rename Modules
 
-Use this panel to rename a *SuiteCRM* module. For example, you may wish 
+Use this panel to rename a *SuiteCRM* module. For example, you may wish
 to rename Accounts as Businesses.
 
 image:RenameModules.png["Rename modules"]
 
-Click on the module you wish to rename. Enter the new singular 
+Click on the module you wish to rename. Enter the new singular
 and plural labels for the module and click btn:[SAVE].
 
 image:RenameModules2.png["Enter new singular and plural labels"]
 
-The new module label will now appear on menus and headings throughout 
+The new module label will now appear on menus and headings throughout
 SuiteCRM.
 
 == Module Builder
@@ -50,14 +50,14 @@ Use the Module Builder to create custom modules in SuiteCRM. The process of crea
 |===
 Furthermore, you can configure the following options:
 * *Importing:* Selecting this option to allow data import into the module.
-* *Navigation Tab:* By default, this option is enabled to create a tab for the module on the top navigation bar. 
+* *Navigation Tab:* By default, this option is enabled to create a tab for the module on the top navigation bar.
 +
 {{%notice note %}} If you want to hide modules temporarily, use <<display_modules_subpanels>> after deployment. Disable this option only for backend modules which will never be shown in the user interface. {{% /notice %}}
 
 . Create new data fields. You can also rename default fields from the template.
 . Customize page layouts for List View, Edit View, Detail View, Sub-panels, Search form, and SuiteCRM Dashlets.
-. Create relationships between the new module and other modules. 
-. Save the package and distribute it. 
+. Create relationships between the new module and other modules.
+. Save the package and distribute it.
 
 {{%notice tip %}} Steps 3-5 are optional and can be done in Studio after deployment. {{% /notice %}}
 
@@ -68,45 +68,45 @@ You can choose one of the following options to distribute the package:
 [cols = "20, 80", frame = "none", grid = "none"]
 
 |===
-| *Deploy* | This option is designed to install the custom module on your local SuiteCRM instance and make it available to users in your organization. After deployment, if needed, you can make further changes to the module in Module Builder and deploy it again to update the installed module. However, note that if you change a deployed custom module in Studio and then re-deploy it from Module Builder, all changes made prior in Studio will be lost. 
+| *Deploy* | This option is designed to install the custom module on your local SuiteCRM instance and make it available to users in your organization. After deployment, if needed, you can make further changes to the module in Module Builder and deploy it again to update the installed module. However, note that if you change a deployed custom module in Studio and then re-deploy it from Module Builder, all changes made prior in Studio will be lost.
 | *Publish* | This option is designed for distribution to specific users or customers. The system creates a zip file, which you can save on your local machine. You can then email it to one or more individuals who can use the Module Loader to upload the zip file into their SuiteCRM instance. After the module is installed through Studio, you can add or remove fields and make other changes to a published module.
-| *Export* | This option is designed for distribution to developers. The system creates a zip file, which you can save on your local machine and share with others. Using the Module Loader, developers can install it on their SuiteCRM instance and customize it further in Module Builder if necessary. The package is visible only in Module Builder and, hence, only administrators can access it until it has been deployed. 
+| *Export* | This option is designed for distribution to developers. The system creates a zip file, which you can save on your local machine and share with others. Using the Module Loader, developers can install it on their SuiteCRM instance and customize it further in Module Builder if necessary. The package is visible only in Module Builder and, hence, only administrators can access it until it has been deployed.
 |===
 
 
 == History Subpanel
 
 image:HistorySubpanel.png["History subpanel settings"]
 
-== Display Modules and Subpanels [[display_modules_subpanels]]
+== Display Modules and Subpanels
 
 Control which modules and subpanels are visible in *SuiteCRM* by dragging
  and dropping modules or subpanels between the Displayed and Hidden columns.
 
-This will show or hide modules in *SuiteCRM* for all users. Should you 
-wish to control access to particular modules, this can be done using 
-Role Management. See link:../roles-and-security-groups[Roles and Security Groups] 
+This will show or hide modules in *SuiteCRM* for all users. Should you
+wish to control access to particular modules, this can be done using
+Role Management. See link:../roles-and-security-groups[Roles and Security Groups]
 for more information.
 
 [cols = "40, 60", frame = "none", grid = "none"]
 |===
 |*Allow users to select modules to apppear in the navigation bar* |
-Selecting this option allows users to customise which module tabs are 
+Selecting this option allows users to customise which module tabs are
 visible from their User Settings.
 |===
 
 image:DisplayModulesandSubpanels.png["Display Modules and Subpanels"]
 
 == Module Loader
 
-Module Loader allows you to install and manage custom modules or plugins for your 
-*SuiteCRM* instance. 
+Module Loader allows you to install and manage custom modules or plugins for your
+*SuiteCRM* instance.
 
-Custom module packages that have been created and modified in Module Builder will 
+Custom module packages that have been created and modified in Module Builder will
 be displayed in Module Loader once they have been deployed.
 
 For more information on producing packages that can be uploaded using Module Loader,
-see the link:../../../developer/module-installer[Developer Guide] 
+see the link:../../../developer/module-installer[Developer Guide]
 
 image:ModuleLoader6.png["Module Loader"]
 
@@ -123,47 +123,47 @@ version number, a short description and whether or not the module can be uninsta
 
 btn:[UNINSTALL] and btn:[DELETE PACKAGE] options will appear.
 
-Click btn:[INSTALL] to install the module. 
+Click btn:[INSTALL] to install the module.
 
 image:ModuleLoader2.png["Module Loader"]
 
 On the next screen, if there are no problems detected with the package and it is
-ready to install you will be asked to click btn:[COMMIT] to complete the installation. 
+ready to install you will be asked to click btn:[COMMIT] to complete the installation.
 
-If any errors occur during installation, they will be displayed here. 
-Otherwise, clicking the *Display Log* link will detail the steps 
+If any errors occur during installation, they will be displayed here.
+Otherwise, clicking the *Display Log* link will detail the steps
 taken in the installation process.
 
 image:ModuleLoader5.png["Module Loader"]
 
 Click btn:[BACK TO MODULE LOADER] to return to the Module Loader screen where
-the newly installed package will appear in the list of installed extensions. 
+the newly installed package will appear in the list of installed extensions.
 
 image:ModuleLoader4.png["Module Loader"]
 
 === Uninstall a Package
 
 For a package to be uninstallable it needs to be defined as uninstallable in the
- package manifest file. For more information regarding the manifest file 
-see the link:../../../developer/module-installer[Developer Guide] 
+ package manifest file. For more information regarding the manifest file
+see the link:../../../developer/module-installer[Developer Guide]
 
 Uninstall a package by clicking the buttons next to the
-package name. 
+package name.
 
-As with the install procedure, you will be asked 
+As with the install procedure, you will be asked
 to confirm the uninstall on the next screen. If the package added any tables to your
-database, you will be asked to if you wish to keep these, and any data within them, for 
+database, you will be asked to if you wish to keep these, and any data within them, for
 example if you are replacing an older version of a module with a new one.
 
 Click btn:[COMMIT] to uninstall the package.
 
-If any errors occur during the uninstall they will be displayed here. 
+If any errors occur during the uninstall they will be displayed here.
 Otherwise, clicking the *Display Log* link will detail the process.
 
 Click btn:[BACK TO MODULE LOADER] to return to the Module Loader screen where
-the newly installed package will appear in the list of installed extensions. 
+the newly installed package will appear in the list of installed extensions.
 
-An uninstalled module will be listed in the lower panel from where it can be 
+An uninstalled module will be listed in the lower panel from where it can be
 re-installed or deleted.
 
 image:ModuleLoader8.png["Module Loader"]
@@ -174,9 +174,9 @@ Use this section to configure the module menus on the top navigation bar.
 
 image:ConfigureModuleMenuFilters.png["Configure Module Menu Filters"]
 
-Drag modules from the list to the required menu, or delete an item by dragging it to 
+Drag modules from the list to the required menu, or delete an item by dragging it to
 the wastepaper bin icon.
-Edit the menu name by clicking the pencil icon next to the module name. 
+Edit the menu name by clicking the pencil icon next to the module name.
 Delete a menu entirely by clicking the wastepaper bin icon next to the module name.
 
 A new custom menu can be added by clicking btn:[ADD FILTER]
@@ -188,9 +188,9 @@ Any changes made will not take effect until you click btn:[SAVE & DEPLOY]
 
 The Dropdown Editor shows all the dropdown lists currently installed on the system.
 
-Click on the dropdown name to edit it. If you are unsure which dropdown you require, it can be 
+Click on the dropdown name to edit it. If you are unsure which dropdown you require, it can be
 easier to edit via Studio where you can find the dropdown by its field name.
-See the link:../../administration-panel/studio/#_adding_a_dropdown_field[Studio guide] for full 
-instructions on adding or editing a dropdown list. 
+See the link:../../administration-panel/studio/#_adding_a_dropdown_field[Studio guide] for full
+instructions on adding or editing a dropdown list.
 
 image:StudioDropdownEditor.png["Dropdown Editor"]

content/admin/administration-panel/Emails/Email.adoc

@@ -113,8 +113,7 @@ Once the settings have been verified, click btn:[SAVE] so that
 these settings are retained before leaving the settings page.
 
 ==== Troubleshooting
-If the test message was not sent successfully, check the log file in
-link:../system#_system_settings[system settings] for any further error messages
+If the test message was not sent successfully, check the log file for any further error messages
 which may assist with resolving the issue.
 
 Verify that all port/protocol settings are correct and that the username/password entered is correct and
@@ -195,7 +194,7 @@ image:OAuthServerConfiguration.png[OAuth Server Configuration]
 
 When setting up with OAuth, you will need the username(email), password and mail server address for the account.
 
-The other required field is `External OAuth Connection`, you can see how to configure this link:InboundEmail-OAuth-HowTo.adoc[here].
+The other required field is `External OAuth Connection`, you can see how to configure this link:../inboundemail-oauth-howto[here].
 
 ==== Email Handling Options
 
@@ -352,7 +351,7 @@ image:EmailCampaignSettings.png[Campaign Settings]
 Scheduled campaign emails are queued here until the scheduled job
 runs to send them out. By default this is the *Run Nightly Mass Email Campaigns* scheduled job.
 
-See the link:../system/#_scheduler[Scheduler] section for
+See the link:../../system/#_scheduler[Scheduler] section for
 further information on scheduled jobs.
 
 Click btn:[SEND QUEUED CAMPAIGN EMAILS] to send them immediately without waiting for the scheduler to do so.

content/user/advanced-modules/Cases with Portal.adoc

@@ -2,7 +2,7 @@
 Title: Cases with Portal
 Weight: 250
 ---
- 
+
 :experimental:   ////this is here to allow btn:[]syntax used below
 
 :imagesdir: /images/en/user
@@ -33,13 +33,13 @@ threaded log of all updates
 Emails Advanced OpenPortal (AOP) uses the standard SuiteCRM
 functionality to send emails and create cases from inbound emails.
 Details on how to configure your outgoing email settings can be found
-link:../../../admin/administration-panel/email/#_outgoing_mail_configuration[here].
+link:../../../admin/administration-panel/emails/email/#_outgoing_mail_configuration[here].
 Details on how to set up a group email account which will
-automatically generate cases can be found link:../../../admin/administration-panel/email/#_group_email_account[here].
+automatically generate cases can be found link:../../../admin/administration-panel/emails/email/#_group_email_account[here].
 
 == Downloading
 
-The plug-in can be downloaded for free from the SuiteCRM site at 
+The plug-in can be downloaded for free from the SuiteCRM site at
 the https://suitecrm.com/resources/suitecrm-joomla-portal-plug-in/[Joomla Portal Plug-in page^].
 
 == Installation & Configuration