Merge pull request #11162 from mendix/db-style-guide-feedback

Apply style guide feedback

Author: dbreseman

content/en/docs/community-tools/contribute-to-mendix-docs/style-guide/product-naming-guide.md

@@ -100,7 +100,7 @@ The Mendix Portal includes Apps (which replaces "Developer Portal"), Control Cen
 
 ### Mendix Studio Pro
 
-"Studio Pro" can be used where regular repetition is necessary in a doc. However, where possible, "Mendix" should be added to the product name.
+Use "Mendix Studio Pro" the first time it's mentioned in a doc. For any subsequent mentions, omit "Mendix" and just use "Studio Pro".
 
 Capitalize in all instances.
 
@@ -151,12 +151,6 @@ This is the term to use to reflect the create-new-app flow UI in the Developer P
 
 Do not use "starter app."
 
-### App User
-
-For a definition of this term, see [Access Management](/developerportal/portfolio-management/access-management/).
-
-Capitalize in all instances.
-
 ### Atlas UI
 
 Capitalize in all instances.

content/en/docs/community-tools/contribute-to-mendix-docs/style-guide/terminology.md

@@ -7,13 +7,7 @@ description: "Usage guidelines for general terminology in Mendix documentation,
 
 ## How to Use This Section
 
-This section contains decisions and usage guidelines for general (non-Mendix specific) terminology, including inclusive language guidelines. For guidelines on Mendix-specific terminology, see the Mendix Product Naming Guide.
-
-Under each term are the following:
-
-Guidelines.
-
-> Example
+This section contains decisions and usage guidelines for general (non-Mendix specific) terminology, including inclusive language guidelines. For guidelines on Mendix-specific terminology, see the [Mendix Product Naming Guide](/community-tools/contribute-to-mendix-docs/style-guide/product-naming-guide/).
 
 ## 1-1 & one-to-one
 
@@ -59,7 +53,7 @@ In the context of development and project management, sometimes using "project"
 
 ## app owner
 
-This is not a formalized/Mendix term (in comparison to [App Contact](/developerportal/general/app-roles/)), so we cannot assume the user knows what this is. This should be defined in general terms and made clearer via context (for example, via the "Copyright" example in the [Insights Hub module documentation](/partners/siemens/mindsphere-module-details/#configuring-the-os-bar)) that it is the user's responsibility to define/interpret what an app owner is for their app.
+This is not a formalized/Mendix term, so we cannot assume the user knows what this is. This should be defined in general terms and made clearer via context (for example, via the "Copyright" example in the [Insights Hub module documentation](/partners/siemens/mindsphere-module-details/#configuring-the-os-bar)) that it is the user's responsibility to define and interpret what an app owner is for their app.
 
 ## article, document, page