Add and fix links

Author: quinntracy

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-10/pluggable-widgets/pluggable-widgets-property-types.md

@@ -441,7 +441,7 @@ When a `dataSource` attribute is specified and configured by the user, it is pas
 
 #### XML Elements
 
-`<translations>` — Allows a user to set a default value for text templates for different languages using `<translation>` elements with a `lang` attribute representing [ISO 639](https://en.wikipedia.org/wiki/ISO_639) code of the language. Available languages are listed in the [Languages Tab](/refguide/app-settings/#languages-tab) in Studio Pro.
+`<translations>` — Allows a user to set a default value for text templates for different languages using `<translation>` elements with a `lang` attribute representing [ISO 639](https://en.wikipedia.org/wiki/ISO_639) code of the language. Available languages are listed in the [Languages Tab](/refguide10/app-settings/#languages-tab) in Studio Pro.
 
 #### Studio Pro UI
 

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-9/pluggable-widgets/pluggable-widgets-property-types-9.md

@@ -448,7 +448,7 @@ When a `dataSource` attribute is specified and configured by the user, it is pas
 
 #### XML Elements
 
-`<translations>` — Allows a user to set a default value for text templates for different languages using `<translation>` elements with a `lang` attribute representing [ISO 639](https://en.wikipedia.org/wiki/ISO_639) code of the language. Available languages are listed in the [Languages Tab](/refguide/app-settings/#languages-tab) in Studio Pro.
+`<translations>` — Allows a user to set a default value for text templates for different languages using `<translation>` elements with a `lang` attribute representing [ISO 639](https://en.wikipedia.org/wiki/ISO_639) code of the language. Available languages are listed in the [Languages Tab](/refguide/languages-tab/) in Studio Pro.
 
 #### Studio Pro UI
 

content/en/docs/refguide/modeling/app-explorer/modules/consume-add-on-modules-and-solutions.md

@@ -18,7 +18,7 @@ When consuming add-on modules and solutions, you may come across the following l
 
 * When debugging add-on and solution modules, you cannot step into microflows, debugging will automatically use **Step Over**.
 * If app modules and add-on modules or solutions have conflicting custom widgets, you are prompted with a warning showing the sources of the conflicts (module and widget package names) to find a workaround. An automatic fix is not implemented.
-* When a constant is hidden, you cannot configure its value in the **App settings**. For more information on app settings, see the [Configuration Tab](/refguide/app-settings/#configurations) section in *App Settings*. 
+* When a constant is hidden, you cannot configure its value in the **App settings**. For more information on app settings, see the [Configuration Tab](/refguide/configurations-tab/) section in *App Settings*. 
 * If there are add-on modules imported into Studio Pro and the application is deployed for Eclipse using menu option **App > Deploy for Eclipse**, there are known build failures in Java source code.
 * If you set the default language to something other than English, and if there is no translation for that language, an error is thrown. To avoid this, set English as the default language.
 

content/en/docs/refguide/modeling/application-logic/expressions/date-creation.md

@@ -6,7 +6,7 @@ weight: 90
 
 ## Introduction
 
-Dates can be created with the `dateTime` and `dateTimeUTC` functions. The difference between them is that  `dateTime` uses the calendar of the session used in the function call, and `dateTimeUTC` uses the UTC calendar. The system session runs as UTC by default, except for scheduled events, which can be configured in the [Scheduled Event Time Zone](/refguide/app-settings/#scheduled) section of **App Settings**.
+Dates can be created with the `dateTime` and `dateTimeUTC` functions. The difference between them is that  `dateTime` uses the calendar of the session used in the function call, and `dateTimeUTC` uses the UTC calendar. The system session runs as UTC by default, except for scheduled events, which can be configured in the [Scheduled Event Time Zone](/refguide/runtime-tab/#scheduled) section of **App Settings**.
 
 {{% alert color="info" %}}
 Do not use `dateTimeUTC` in client-side expressions (for example, in nanoflows) if you want to assign the output to (or compare the output with) an attribute of type **Date and time** where **Localize** is disabled. In the client, the localization functionality is built into the attribute type itself, and using UTC functions causes the time zone conversion to be handled twice.

content/en/docs/refguide10/general/mx-command-line-tool/private-values.md

@@ -9,7 +9,7 @@ description: "Describes the commands related to private values for the mx comman
 
 The commands in this group are related to showing and deleting private values.
 
-Studio Pro stores private values, such as values for [private constants](/refguide10/configurations-tab/#constants), in an encrypted way in the user's local app data. These private values are defined by:
+Studio Pro stores private values, such as values for [private constants](/refguide10/configurations-tab/), in an encrypted way in the user's local app data. These private values are defined by:
 
 * The path of the `.mpr` file of the app
 * The version of Studio Pro