From 899a7bb47eea817294fe4c839f67e65667ca2df5 Mon Sep 17 00:00:00 2001 From: estelle Date: Tue, 9 Dec 2025 17:02:31 +0100 Subject: [PATCH] Remove EASY from glossary --- files/en-us/glossary/accessibility_tree/index.md | 2 +- files/en-us/glossary/color_wheel/index.md | 2 +- files/en-us/glossary/continuous_integration/index.md | 2 +- files/en-us/glossary/css_preprocessor/index.md | 2 +- files/en-us/glossary/database/index.md | 2 +- files/en-us/glossary/localization/index.md | 2 +- files/en-us/glossary/progressive_web_apps/index.md | 2 +- files/en-us/glossary/sloppy_mode/index.md | 2 +- files/en-us/glossary/source_map/index.md | 2 +- files/en-us/glossary/ssg/index.md | 2 +- files/en-us/glossary/ux/index.md | 2 +- 11 files changed, 11 insertions(+), 11 deletions(-) diff --git a/files/en-us/glossary/accessibility_tree/index.md b/files/en-us/glossary/accessibility_tree/index.md index 2e0e4f5ad82b4b4..fc4dc479b6fef10 100644 --- a/files/en-us/glossary/accessibility_tree/index.md +++ b/files/en-us/glossary/accessibility_tree/index.md @@ -22,7 +22,7 @@ There are four properties in an accessibility tree object: Additionally, the accessibility tree often contains information on what can be done with an element: a link can be _followed_, a text input can be _typed into_, etc. -While still in draft form within the Web Incubator Community Group as of April 2022, the **[Accessibility Object Model](https://wicg.github.io/aom/explainer.html) (AOM)** intends to incubate APIs that make it easier to express accessibility semantics and potentially allow read access to the computed accessibility tree. +While still in draft form within the Web Incubator Community Group as of April 2022, the **[Accessibility Object Model](https://wicg.github.io/aom/explainer.html) (AOM)** intends to incubate APIs that enable expressing accessibility semantics and potentially allow read access to the computed accessibility tree. ## See also diff --git a/files/en-us/glossary/color_wheel/index.md b/files/en-us/glossary/color_wheel/index.md index 3e6ded4431fd35f..48dfd0327b7aad3 100644 --- a/files/en-us/glossary/color_wheel/index.md +++ b/files/en-us/glossary/color_wheel/index.md @@ -9,7 +9,7 @@ A **color wheel**, or a _color circle_, represents a palette of colors in chart Color wheels are convenient for comparing colors expressed in polar or cylindrical coordinates, like [`hsl()`](/en-US/docs/Web/CSS/Reference/Values/color_value/hsl), [`hwb()`](/en-US/docs/Web/CSS/Reference/Values/color_value/hwb), or [`lch()`](/en-US/docs/Web/CSS/Reference/Values/color_value/lch). -In such cases, _complementary colors_ are often found opposite on the same diameter. Similarly, _monochromatic colors_ – colors of the same _tone_ but of different _shades_ – are located on the same radius, and _triadic colors_ – three colors evenly spaced around the color wheel that lead to colors that work well together – are also easy to find. +In such cases, _complementary colors_ are often found opposite on the same diameter. Similarly, _monochromatic colors_ – colors of the same _tone_ but of different _shades_ – are located on the same radius, and _triadic colors_ – three colors evenly spaced around the color wheel that lead to colors that work well together. Color wheels are used in real life when we want to choose between different hues. For example, when selecting wall paint or the color for a piece of furniture. diff --git a/files/en-us/glossary/continuous_integration/index.md b/files/en-us/glossary/continuous_integration/index.md index a7d5d7795609981..8a7a9fa13d7cfad 100644 --- a/files/en-us/glossary/continuous_integration/index.md +++ b/files/en-us/glossary/continuous_integration/index.md @@ -7,7 +7,7 @@ sidebar: glossarysidebar Continuous integration (CI) is a software development practice in which changes to the source are frequently integrated into the main codebase. -It's an important practice whenever a team of developers is working on a shared codebase. In this situation, different developers might be making overlapping changes to the code at the same time, each in their personal branches. Frequent integration of each developer's changes makes it much less likely that conflicts will occur, and much easier to resolve them when they do. +It's an important practice whenever a team of developers is working on a shared codebase. In this situation, different developers might be making overlapping changes to the code at the same time, each in their personal branches. Frequent integration of each developer's changes makes it much less likely that conflicts will occur, and much more intuitive to resolve them when they do. As [Martin Fowler observes](https://martinfowler.com/articles/continuousIntegration.html#EveryonePushesCommitsToTheMainlineEveryDay): diff --git a/files/en-us/glossary/css_preprocessor/index.md b/files/en-us/glossary/css_preprocessor/index.md index 167b6a42674078b..474dedc27fdbf4e 100644 --- a/files/en-us/glossary/css_preprocessor/index.md +++ b/files/en-us/glossary/css_preprocessor/index.md @@ -7,7 +7,7 @@ sidebar: glossarysidebar A **CSS preprocessor** is a program that lets you generate {{Glossary("CSS")}} from the preprocessor's own unique {{Glossary("syntax")}}. -There are many CSS preprocessors to choose from, however most CSS preprocessors will add some features that don't exist in pure CSS, such as mixin, nesting selector, inheritance selector, and so on. These features make the CSS structure more readable and easier to maintain. +There are many CSS preprocessors to choose from, however most CSS preprocessors will add some features that don't exist in pure CSS, such as mixin, nesting selector, inheritance selector, and so on. These features make the CSS structure more readable and maintainable. To use a CSS preprocessor, you must install a CSS compiler on your web {{Glossary("server")}}; Or use the CSS preprocessor to compile on the development environment, and then upload compiled CSS file to the web server. diff --git a/files/en-us/glossary/database/index.md b/files/en-us/glossary/database/index.md index 03ba2b73512986d..15a74e6e321567f 100644 --- a/files/en-us/glossary/database/index.md +++ b/files/en-us/glossary/database/index.md @@ -5,7 +5,7 @@ page-type: glossary-definition sidebar: glossarysidebar --- -A **database** is a storing system that collects organized data, to make some works easier like searching, structure, and extend. +A **database** is a storing system that collects organized data, enabling tasks like searching, structure, and extend. In web development, most databases use the relational database management system (RDBMS) to organize data and programming in {{glossary("SQL")}}. Some databases, however, don't follow the former mechanism to organized data, which called NoSQL. diff --git a/files/en-us/glossary/localization/index.md b/files/en-us/glossary/localization/index.md index 94e0a2077239ae8..2d9cf9506beba50 100644 --- a/files/en-us/glossary/localization/index.md +++ b/files/en-us/glossary/localization/index.md @@ -25,7 +25,7 @@ The following are common factors to consider: - local holidays - personal names -The complementary practice, of designing a system so it is easy to localize, is called {{glossary("Internationalization")}}. +The complementary practice, of designing a system so it is more readily localizable, is called {{glossary("Internationalization")}}. ## See also diff --git a/files/en-us/glossary/progressive_web_apps/index.md b/files/en-us/glossary/progressive_web_apps/index.md index 10ea0f2adba6470..1f7374eabdbc4bc 100644 --- a/files/en-us/glossary/progressive_web_apps/index.md +++ b/files/en-us/glossary/progressive_web_apps/index.md @@ -9,7 +9,7 @@ sidebar: glossarysidebar These kinds of apps enjoy all the best parts of the Web — such as discoverability via search engines, being linkable via {{Glossary("URL")}}s, and working across multiple form factors, but are progressively enhanced with modern APIs (such as [Service Workers](/en-US/docs/Web/API/Service_Worker_API) and [Push](/en-US/docs/Web/API/Push_API)). -These features include being installable, working offline, and being easy to sync with and re-engage the user from the server. +These features include being installable, working offline, and syncing with and re-engaging the user from the server. ## See also diff --git a/files/en-us/glossary/sloppy_mode/index.md b/files/en-us/glossary/sloppy_mode/index.md index 210674c37860c4f..d7db74ea942a907 100644 --- a/files/en-us/glossary/sloppy_mode/index.md +++ b/files/en-us/glossary/sloppy_mode/index.md @@ -5,7 +5,7 @@ page-type: glossary-definition sidebar: glossarysidebar --- -{{Glossary("ECMAScript")}} 5 and later let scripts opt in to a new [strict mode](/en-US/docs/Web/JavaScript/Reference/Strict_mode), which alters the semantics of JavaScript in several ways to improve its resiliency and which make it easier to understand what's going on when there are problems. +{{Glossary("ECMAScript")}} 5 and later let scripts opt in to a new [strict mode](/en-US/docs/Web/JavaScript/Reference/Strict_mode), which alters the semantics of JavaScript in several ways to improve its resiliency and which make what's going on more understandable when there are problems. The normal, non-strict mode of JavaScript is sometimes referred to as **sloppy mode**. This isn't an official designation, but you are likely to come across it if you spend time doing serious JavaScript code. diff --git a/files/en-us/glossary/source_map/index.md b/files/en-us/glossary/source_map/index.md index d6163ce4c4cd066..fe64f7acdb23b0c 100644 --- a/files/en-us/glossary/source_map/index.md +++ b/files/en-us/glossary/source_map/index.md @@ -13,7 +13,7 @@ Code executed by the browser is often transformed in some way from the original - To support older browsers by transforming modern features into older equivalents. - To use languages that browsers don't support, like {{Glossary("TypeScript")}} or [Sass](https://sass-lang.com/). -In these situations, debugging the original source is much easier than the source in the transformed state that the browser has downloaded. +In these situations, debugging the original source is more intuitive than the source in the transformed state that the browser has downloaded. Browsers detect a source map via the {{HTTPHeader("SourceMap")}} HTTP header for a resource, or a `sourceMappingURL` annotation in the generated code. ## Example diff --git a/files/en-us/glossary/ssg/index.md b/files/en-us/glossary/ssg/index.md index b83035795be2629..fb157c6cf0c19bb 100644 --- a/files/en-us/glossary/ssg/index.md +++ b/files/en-us/glossary/ssg/index.md @@ -7,7 +7,7 @@ sidebar: glossarysidebar A **static site generator** (SSG) is a software used to generate _static_ websites. A static website is comprised of {{glossary("HTML")}}, {{glossary("CSS")}}, and {{glossary("JavaScript")}} files. Most importantly static sites do not have [server-side logic](/en-US/docs/Learn_web_development/Extensions/Server-side), so for any given URL, all users will receive the same content. Authors write content in any form accepted by the generator, such as Markdown, reStructuredText, HTML, (and sometimes even [React](/en-US/docs/Learn_web_development/Core/Frameworks_libraries/React_getting_started), and so on), and the generator compiles them into a set of optimized static files that can be rendered by the browser. -Static sites are commonly used for blogs, documentation, and other content-driven websites, which don't have data that needs to be fetched or generated server-side. They are fast, secure, and easy to deploy, because they can be served from a {{glossary("CDN")}}. +Static sites are commonly used for blogs, documentation, and other content-driven websites, which don't have data that needs to be fetched or generated server-side. They are fast, secure, and easier to deploy, because they can be served from a {{glossary("CDN")}}. ## See also diff --git a/files/en-us/glossary/ux/index.md b/files/en-us/glossary/ux/index.md index a5835345d795c3f..f742af4daddeb59 100644 --- a/files/en-us/glossary/ux/index.md +++ b/files/en-us/glossary/ux/index.md @@ -5,7 +5,7 @@ page-type: glossary-definition sidebar: glossarysidebar --- -**UX** is an acronym that stands for User eXperience. It is the study of the interaction between users and a system. Its goal is to make a system easy to interact with from the user's point of view. +**UX** is an acronym that stands for User eXperience. It is the study of the interaction between users and a system. Its goal is to make a system intuitive and easy to interact with from the user's point of view. The system can be any kind of product or application that an end user is meant to interact with. UX studies undertaken on a web page for example can demonstrate whether it is easy for users to understand the page, navigate to different areas, and complete common tasks, and where such processes could have less friction.