Skip to content

Update glossary.mdx #567

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 7, 2025
Merged

Update glossary.mdx #567

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions website/docs/glossary.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ Canary testing is a software deployment technique where updates or new features

#### [CI/CD Pipeline](./glossary/ci-cd-pipeline.mdx)

A Continuous Integration and Continuous Deployment pipeline (CI/CD) is a set of steps that must be followed to deliver a new software version to customers.
A CI/CD (Continuous Integration and Continuous Deployment) pipeline is a set of steps that must be followed to deliver a new software version to customers.

#### [Continuous Delivery](https://configcat.com/blog/2022/06/13/decoupling-feature-releases-from-deployment/)

Expand All @@ -56,7 +56,7 @@ Continuous Integration refers to the regular merging of code changes into a cent

#### [Dark Launch](https://configcat.com/blog/2022/06/13/decoupling-feature-releases-from-deployment/#feature-release-with-dark-launch)

A Dark Launch is rolled out stealthily by first releasing a feature to a subset of users before a full release to see how they react to it.
A dark launch involves releasing a feature to a subset of users before a full release to test reactions.

#### [Developer Advocate](https://configcat.com/blog/2023/07/11/role-of-developer-advocates/)

Expand Down Expand Up @@ -127,9 +127,9 @@ A kill switch is a mechanism that can be used to quickly disable a feature or an

## M

#### [Multi Armed Bandit](./glossary/multi-armed-bandit.mdx)
#### [Multi-Armed Bandit](./glossary/multi-armed-bandit.mdx)

The Multi-Armed Bandit (MAB) is a machine learning framework that involves an agent making selections, referred to as "arms," with the goal of maximizing its long-term cumulative reward
The Multi-Armed Bandit (MAB) is a machine learning framework that involves an agent making selections, referred to as "arms," with the goal of maximizing long-term cumulative rewards.

## N

Expand Down Expand Up @@ -163,7 +163,7 @@ React feature flags are conditional codes used in React.js applications to enabl

#### [Release Manager](./glossary/release-manager.mdx)

A release manager is an IT professional responsible for defining and executing the software release process within a company, ensuring smooth deployment and high quality releases.
A release manager is an IT professional responsible for defining and executing the software release process within a company, ensuring smooth deployment and high-quality releases.

#### [Remote Configuration](./glossary/remote-configuration.mdx)

Expand Down Expand Up @@ -197,7 +197,7 @@ Software as a Service (SaaS) is a cloud-based delivery model where applications

#### [Staging Environment](./glossary/what-is-a-staging-environment.mdx)

A staging environment is a dry run for your code under the closest possible parameters to its real-world application. It is a near-perfect replica of the servers, infrastructure, architecture, and application of the actual use environment of your code. The key difference is that it is completely walled off from the front-facing actual environment.
A staging environment is a dry run for your code under the closest possible parameters to its real-world application. It is a near-perfect replica of the servers, infrastructure, architecture, and application of the actual production environment your code will run in. The key difference is that it is completely walled off from the front-facing actual environment.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❤️


## T

Expand All @@ -207,9 +207,9 @@ Testing in production is the practice of evaluating software in its live environ

#### [Type I and Type II Errors](./glossary/type-i-and-type-ii-errors.mdx)

A Type I error occurs when the null hypothesis is incorrectly rejected while it is actually true, while a Type II error occurs when the null hypothesis is wrongly not rejected while it is actually false.
A Type I error occurs when the null hypothesis is incorrectly rejected, even though it is actually true. A Type II error occurs when the null hypothesis is wrongly not rejected while it is actually false.

#### [Trunk Based Development](https://configcat.com/trunk-based-development/)
#### [Trunk-Based Development](https://configcat.com/trunk-based-development/)

Trunk-based development is a version control technique where developers regularly merge small updates into a central "trunk" or main branch.

Expand Down