Merge pull request #135 from commerce-docs/ds_glossary

Remove glossary links

Author: dshevtsov

src/pages/architecture/basics/diagrams.md

@@ -5,7 +5,7 @@ description: Visualize the architectural layers of Adobe Commerce and Magento Op
 
 # Architectural diagram
 
-Depending upon your role and purpose for learning more about Adobe Commerce and Magento Open Source, there are several different ways to view the architecture. For example, a developer who wants to create new modules or perhaps customize an existing [module](https://glossary.magento.com/module) will want to understand the architecture of a module itself, and how it fits into the larger view, with the Adobe Commerce and Magento Open Source framework (Commerce framework) and other components. However, a merchant who wants to quickly build an online storefront wants to view the collection of components from a higher level, and understand the components that impact the look, feel, and user interaction components.
+Depending upon your role and purpose for learning more about Adobe Commerce and Magento Open Source, there are several different ways to view the architecture. For example, a developer who wants to create new modules or perhaps customize an existing module will want to understand the architecture of a module itself, and how it fits into the larger view, with the Adobe Commerce and Magento Open Source framework (Commerce framework) and other components. However, a merchant who wants to quickly build an online storefront wants to view the collection of components from a higher level, and understand the components that impact the look, feel, and user interaction components.
 
 The following diagram illustrates the components and shows the "layers" or tiers in the Commerce framework.
 

src/pages/architecture/basics/frontend-customization.md

@@ -5,15 +5,15 @@ description: Discover tools designed to help you customize your Adobe Commerce o
 
 # Frontend customization
 
-The [frontend](https://glossary.magento.com/frontend) is designed to optimize [storefront](https://glossary.magento.com/storefront) customization, with highly extensible *themes* being the central customization mechanism.
+The frontend is designed to optimize storefront customization, with highly extensible *themes* being the central customization mechanism.
 
 Merchants are encouraged to use components and themes to extend and transform the appearance of their storefronts.
 
 ## Storefront customization tools
 
 Adobe provides several tools to help you significantly jumpstart the storefront customization process:
 
-*  [Blank theme](https://glossary.magento.com/theme)
+*  Blank theme
 
 *  [UI components](https://developer.adobe.com/commerce/frontend-core/ui-components/)
 
@@ -32,25 +32,25 @@ Using standard coding and styling tools can help:
 *  Enforce for consistency in design across your storefronts
 *  Simplify (and speed up) the design process
 
-This component [library](https://glossary.magento.com/library) contains standard reusable components for form features, such as fields and buttons, and navigation elements. The UI library is a set of generic web components and Commerce-specific patterns, which simplifies the process of theme creation and customization.
+This component library contains standard reusable components for form features, such as fields and buttons, and navigation elements. The UI library is a set of generic web components and Commerce-specific patterns, which simplifies the process of theme creation and customization.
 
 See [Overview of UI components](https://developer.adobe.com/commerce/frontend-core/ui-components/) for details about this library.
 
 ### Admin pattern library
 
 A *pattern library* is a collection of user interface (UI) design patterns that can be re-used in locations throughout your product installation. The [Admin Pattern Library](https://developer.adobe.com/commerce/admin-developer/pattern-library/) defines examples of components that administrators working with the storefront can use.
 
-Form elements included in the [Admin](https://glossary.magento.com/magento-admin) pattern library include:
+Form elements included in the Admin pattern library include:
 
 *  address form
 *  button bar
 *  container
 *  tabs
 *  sign-in form
 
-Users of the default storefront encounter examples of these form elements throughout the product. These patterns provide a valuable language of software components (and indirectly, user experiences) for [extension](https://glossary.magento.com/extension) developers and administrators.
+Users of the default storefront encounter examples of these form elements throughout the product. These patterns provide a valuable language of software components (and indirectly, user experiences) for extension developers and administrators.
 
-The [Admin Pattern library](https://glossary.magento.com/admin) is built on the Less preprocessor and implemented as a [module](https://glossary.magento.com/module). You can download a free, current version of this module from [Commerce Marketplace](https://marketplace.magento.com/).
+The Admin Pattern library is built on the Less preprocessor and implemented as a module. You can download a free, current version of this module from [Commerce Marketplace](https://marketplace.magento.com/).
 
 See [Admin Pattern Library](https://developer.adobe.com/commerce/admin-developer/pattern-library/) for more information on using this library.
 
@@ -60,11 +60,11 @@ These four levels of potential storefront customization are listed in order to i
 
 ### Extend CSS
 
-Commerce supplies a default [theme](https://glossary.magento.com/theme) and a Less-based CSS. You can substantially change a storefront using CSS only. This uncomplicated strategy might suit projects with a limited budget, or might interest developers who create different skins for a site. A small business enter this process of storefront customization by buying a third-party developed theme from Commerce Marketplace to extend the default values.
+Commerce supplies a default theme and a Less-based CSS. You can substantially change a storefront using CSS only. This uncomplicated strategy might suit projects with a limited budget, or might interest developers who create different skins for a site. A small business enter this process of storefront customization by buying a third-party developed theme from Commerce Marketplace to extend the default values.
 
 ### Replace PHTML template files
 
-In addition to extending the default CSS, you can generate different HTML [markup](https://glossary.magento.com/markup). For example, you might need to add a missing CSS class name, or add an extra `<div>` tag to achieve some visual effect. You might also need to tweak some [JavaScript](https://glossary.magento.com/javascript/) to cope with different HTML markup. This change is more demanding than simply extending CSS, but is still within the grasp of smaller projects and leaner teams.
+In addition to extending the default CSS, you can generate different HTML markup. For example, you might need to add a missing CSS class name, or add an extra `<div>` tag to achieve some visual effect. You might also need to tweak some JavaScript to cope with different HTML markup. This change is more demanding than simply extending CSS, but is still within the grasp of smaller projects and leaner teams.
 
 ### Replace CSS
 
@@ -78,4 +78,4 @@ Delivering a sharply different shopping experience than the default Commerce ins
 
 <InlineAlert variant="success" slots="text"/>
 
-Any customization of your storefront will work optimally, and provide the easiest path for later upgrades, if you follow the best practice of consistently compartmentalizing code by type. For example, keep all HTML in [PHTML](https://glossary.magento.com/phtml) files; keep all JavaScript in JavaScript files.
+Any customization of your storefront will work optimally, and provide the easiest path for later upgrades, if you follow the best practice of consistently compartmentalizing code by type. For example, keep all HTML in PHTML files; keep all JavaScript in JavaScript files.

src/pages/architecture/basics/security.md

@@ -17,7 +17,7 @@ Adobe has strengthened the hashing algorithms (SHA-256) used in password managem
 
 ### Improved prevention of cross-site scripting (XSS) attacks by making escaped data the default
 
-The Commerce framework has adopted conventions that regulate the escaping of data in output. These conventions include the ability to escape  output for [HTML](https://glossary.magento.com/html) pages (HTML, JSON, and JavaScript) and email. Where possible, escaping is transparent to client code. See [Security measures against XSS attacks](https://developer.adobe.com/commerce/php/development/security/cross-site-scripting/) in the [Frontend](https://glossary.magento.com/frontend) Developer Guide.
+The Commerce framework has adopted conventions that regulate the escaping of data in output. These conventions include the ability to escape  output for HTML pages (HTML, JSON, and JavaScript) and email. Where possible, escaping is transparent to client code. See [Security measures against XSS attacks](https://developer.adobe.com/commerce/php/development/security/cross-site-scripting/) in the Frontend Developer Guide.
 
 ### More flexible file system ownership and permissions
 
@@ -35,4 +35,4 @@ The Commerce framework safeguards your store from clickjacking attacks by using
 
 ### Use of non-default Admin URL
 
-A simple [Admin](https://glossary.magento.com/magento-admin) [URL](https://glossary.magento.com/url) (like `admin` or `backend`) makes it easy to target attacks on specific locations using automated password guessing. To prevent against this type of attack, the Commerce framework by default creates a random Admin URI when you install the product. The CLI command `php bin/magento info:adminuri` is provided so that you can  see the URI if you forget it. You can also use the CLI to change this URI.  Although the use of a non-default admin URL will not secure the site, its use will help prevent large-scale automated attacks. See [Display or change the Admin URI](https://devdocs.magento.com/guides/v2.4/install-gde/install/cli/install-cli-adminurl.html) in Configuration Guide for more information.
+A simple Admin URL (like `admin` or `backend`) makes it easy to target attacks on specific locations using automated password guessing. To prevent against this type of attack, the Commerce framework by default creates a random Admin URI when you install the product. The CLI command `php bin/magento info:adminuri` is provided so that you can  see the URI if you forget it. You can also use the CLI to change this URI.  Although the use of a non-default admin URL will not secure the site, its use will help prevent large-scale automated attacks. See [Display or change the Admin URI](https://devdocs.magento.com/guides/v2.4/install-gde/install/cli/install-cli-adminurl.html) in Configuration Guide for more information.

src/pages/architecture/framework.md

@@ -5,10 +5,10 @@ description: Learn how the Commerce framework controls the way application compo
 
 # Commerce framework
 
-The Adobe Commerce and Magento Open Source framework (Commerce framework) controls how application components interact, including request flow, routing, indexing, caching, and [exception](https://glossary.magento.com/exception) handling. It provides services that reduce the effort of creating modules that contain business logic, contributing to the goal of both making Commerce code more modular as well as decreasing dependencies.
+The Adobe Commerce and Magento Open Source framework (Commerce framework) controls how application components interact, including request flow, routing, indexing, caching, and exception handling. It provides services that reduce the effort of creating modules that contain business logic, contributing to the goal of both making Commerce code more modular as well as decreasing dependencies.
 
-This primarily [PHP](https://glossary.magento.com/php) software component is organized into logical groups called *libraries*, which all modules can call.  Most of the framework code sits under the domain layer or encloses the presentation, service, and domain layers. The framework contains no business logic.
-(Although the Commerce framework does not contain resource models, it does contain a [library](https://glossary.magento.com/library) of code to help implement a resource model.)
+This primarily PHP software component is organized into logical groups called *libraries*, which all modules can call.  Most of the framework code sits under the domain layer or encloses the presentation, service, and domain layers. The framework contains no business logic.
+(Although the Commerce framework does not contain resource models, it does contain a library of code to help implement a resource model.)
 
 <InlineAlert variant="success" slots="text"/>
 
@@ -42,19 +42,19 @@ lib/
     ../web
 ```
 
-*  `/vendor/magento/framework`  contains only PHP code. These are libraries of code plus the application entry point that routes requests to modules (that in turn call the Framework libraries). For example,  libraries in the Framework help implement a resource model (base classes and interfaces to inherit from) but not the resource models themselves. Certain libraries also support [CSS](https://glossary.magento.com/css) rendering.
+*  `/vendor/magento/framework`  contains only PHP code. These are libraries of code plus the application entry point that routes requests to modules (that in turn call the Framework libraries). For example,  libraries in the Framework help implement a resource model (base classes and interfaces to inherit from) but not the resource models themselves. Certain libraries also support CSS rendering.
 
-*  `/lib/internal` contains some non-PHP as well as PHP components. Non-PHP framework libraries includes [JavaScript](https://glossary.magento.com/javascript) and LESS/CSS.
+*  `/lib/internal` contains some non-PHP as well as PHP components. Non-PHP framework libraries includes JavaScript and LESS/CSS.
 
 *  `/lib/web` contains JavaScript and CSS/LESS files. These files reside  under `web` and not `internal` because they are accessible from a web browser, while the PHP code under `internal` is not. (Any code that a web browser must access should be under `web`, while everything else under `internal`.)
 
 <InlineAlert variant="success" slots="text"/>
 
-The `vendor/magento/framework` directory maps to the `Magento\Framework` [namespace](https://glossary.magento.com/namespace).
+The `vendor/magento/framework` directory maps to the `Magento\Framework` namespace.
 
 ## Framework highlights
 
-The Commerce framework (`lib/internal/Magento/Framework/`) provides a robust range of functionality. If you are an [extension](https://glossary.magento.com/extension) developer, you may be interested in this subset of Framework namespaces.
+The Commerce framework (`lib/internal/Magento/Framework/`) provides a robust range of functionality. If you are an extension developer, you may be interested in this subset of Framework namespaces.
 
 |Namespace|Purpose|
 |--- |--- |

src/pages/architecture/layers/domain.md

@@ -5,7 +5,7 @@ description: Learn about the architectural domain layer of the Commerce framewor
 
 # Domain layer
 
-The domain layer holds the business logic layer of a [module](https://glossary.magento.com/module). It typically does not contain resource-specific or database-specific information. Its primary functions include:
+The domain layer holds the business logic layer of a module. It typically does not contain resource-specific or database-specific information. Its primary functions include:
 
 *  Defining the generic data objects, or models, that contain business logic. This logic defines which operations can be performed on particular types of data, such as a Customer object. These models contain generic information only. Applications can also use SOAP or RESTful endpoints to request data from models.
 

src/pages/architecture/layers/index.md

@@ -7,7 +7,7 @@ description: Learn about layered application design and details about each layer
 
 At its highest level, the Adobe Commerce and Magento Open Source framework (Commerce framework) architecture consists of the core product code plus optional *modules*. These optional modules enhance or replace the basic product code.
 
-If you are substantially customizing the basic Adobe Commerce or Magento Open Source product, [module](https://glossary.magento.com/module) development will be your central focus. Modules organize code that supports a particular task or feature. A module can include code to change the look-and-feel of your [storefront](https://glossary.magento.com/storefront) as well as its fundamental behavior.
+If you are substantially customizing the basic Adobe Commerce or Magento Open Source product, module development will be your central focus. Modules organize code that supports a particular task or feature. A module can include code to change the look-and-feel of your storefront as well as its fundamental behavior.
 
 Your modules function with the core product code, which is organized into layers. Understanding layered software pattern is essential for understanding basic Adobe Commerce and Magento Open Source product organization.
 
@@ -17,6 +17,6 @@ Layered software is a popular, widely discussed principle in software developmen
 
 Layered application design offers many advantages, but users of the Commerce framework will appreciate:
 
-*  Stringent separation of business logic from presentation logic simplifies the customization process. For example, you can alter your storefront appearance without affecting any of the [backend](https://glossary.magento.com/backend) business logic.
+*  Stringent separation of business logic from presentation logic simplifies the customization process. For example, you can alter your storefront appearance without affecting any of the backend business logic.
 
-*  Clear organization of code predictably points [extension](https://glossary.magento.com/extension) developers to code location.
+*  Clear organization of code predictably points extension developers to code location.