Revert for Mx10

Author: quinntracy

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

@@ -425,7 +425,7 @@ Support for the `dataSource` attribute was introduced in Mendix 8.14.
 
 #### 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/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/refguide/modeling/best-practices/dev-best-practices/app-setup.md

@@ -39,6 +39,6 @@ Each user role should correspond to only one module role per module. In other wo
 
 Always store secret information in a safe place. A safe place is the database. Use the [Encryption](https://marketplace.mendix.com/link/component/1011) module to encrypt, store, retrieve, and decrypt the information.
 
-You can also store [private constants](/refguide/configuration/#constants) in configurations. These are encrypted and stored on your local machine so will not be shared with others.
+You can also store [private constants](/refguide/configurations-tab/#constants) in configurations. These are encrypted and stored on your local machine so will not be shared with others.
 
 Using either the default value of a constant or the project's shared configuration settings is unsafe. Both these places are readable by others and visible in the version management copies. 

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/), 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/configuration/#constants), 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