Fix broken links

Author: quinntracy

content/en/docs/appstore/use-content/platform-supported-content/modules/document-generation.md

@@ -376,7 +376,7 @@ If you encounter any issues while [registering your app environment](#register-a
 
 In general, we recommend that you perform the following steps if you get any issues during runtime:
 
-1. Temporarily set the log level of `DocumentGeneration` log node to [trace](/howto/monitoring-troubleshooting/log-levels/#level). This should give more insight at what stage the action fails.
+1. Temporarily set the log level of `DocumentGeneration` log node to [trace](/refguide/log-levels/#level). This should give more insight at what stage the action fails.
 2. Temporarily add the page microflow that is configured in the action to the app navigation, or make it accessible via a button. This can help to verify that the page itself loads correctly, and can for example outline misconfiguration of entity access, widgets, etc. Make sure that you access the page with the same user you provided to the `Generate as user` parameter in the action.
 
 #### Exceptions
@@ -445,7 +445,7 @@ com.mendix.modules.microflowengine.MicroflowException: com.mendix.systemwideinte
 	at DocumentGenerationTest.ACT_TestDocument_WrongLayout (JavaAction : 'Generate PDF from page')
 ```
 
-We recommend that you temporarily set the log level of the `DocumentGeneration` log node to [trace](/howto/monitoring-troubleshooting/log-levels/#level). This should give more insight at what stage the action fails.
+We recommend that you temporarily set the log level of the `DocumentGeneration` log node to [trace](/refguide/log-levels/#level). This should give more insight at what stage the action fails.
 
 #### Cloud Service Errors
 

content/en/docs/refguide/modeling/integration/machine-learning-kit/using-ml-kit/_index.md

@@ -259,8 +259,6 @@ Machine learning models might be placed in the core of a Mendix application that
 
 In the section below, there are tips for Mendix developers to get insights about inference calls in the development and production phases. You might need to observe the inputs/outputs of a model that is used in an *ML Kit* activity, assess the performance (latency) of making a prediction, or debug an individual pre/post-processing unit on a test sample to verify that the Microflow works and to catch potential bugs in development time before rolling out the application to the production environments.
 
-See the [Monitoring and Troubleshooting](/howto/monitoring-troubleshooting/) guide for general monitoring and troubleshooting tips in Studio Pro.
-
 ### Troubleshooting
 
 The [Errors Pane](/refguide/errors-pane/) in Studio Pro shares informative messages about the metadata of the ML models that are consumed by the **Call ML Model** activity. Warning messages do not block deployment, but the application may not work seamlessly. All error messages have to be resolved in order to execute applications in local environments or deploy applications into the production environments.

content/en/docs/refguide/runtime/logging/_index.md

@@ -9,7 +9,7 @@ description: "Describes what the various log levels of the runtime will show as
 Below we describe what the various log levels of the runtime will show as output.
 During development, these log levels can be set in the console (advanced -> set log levels), when deployed on a server, please refer to the [Deployment](/developerportal/deploy/mendix-cloud-deploy/) pages.
 
-You can also set log levels to provide more or less information when testing locally using the console in Studio Pro. See [Configuring Log Levels Within Studio Pro](/howto/monitoring-troubleshooting/log-levels/#configure-log-levels-from-studio-pro) in *How To Set Log Levels* for more information.
+You can also set log levels to provide more or less information when testing locally using the console in Studio Pro. See [Configuring Log Levels Within Studio Pro](/refguide/log-levels/#configure-log-levels-from-studio-pro) in *How To Set Log Levels* for more information.
 
 ## Log Levels {#log-levels}
 

content/en/docs/refguide9/runtime/logging.md

@@ -9,7 +9,7 @@ description: "Describes what the various log levels of the runtime will show as
 Below we describe what the various log levels of the runtime will show as output.
 During development, these log levels can be set in the console (advanced -> set log levels), when deployed on a server, please refer to the [Deployment](/developerportal/deploy/mendix-cloud-deploy/) pages.
 
-You can also set log levels to provide more or less information when testing locally using the console in Studio Pro. See [Configuring Log Levels Within Studio Pro](/howto/monitoring-troubleshooting/log-levels/#configure-log-levels-from-studio-pro) in *How To Set Log Levels* for more information.
+You can also set log levels to provide more or less information when testing locally using the console in Studio Pro. See [Configuring Log Levels Within Studio Pro](/refguide/log-levels/#configure-log-levels-from-studio-pro) in *How To Set Log Levels* for more information.
 
 ## Log Levels {#log-levels}