ENGDOCS-740 (#14937)

* ENGDOCS-740

_data/glossary.yaml

@@ -99,6 +99,8 @@ Docker ID: |
   Your free Docker ID grants you access to Docker Hub repositories and some beta programs. All you need is an email address.
 Docker Official Images: |
   The Docker Official Images are a curated set of Docker repositories hosted on [Docker Hub](#docker-hub). Docker, Inc. sponsors a dedicated team that is responsible for reviewing and publishing all content in the Docker Official Images. This team works in collaboration with upstream software maintainers, security experts, and the broader Docker community.
+Docker Open Source Images: |
+  Docker Open Source Images are published and maintained by organizations that are a member of the Docker Open Source Program.
 Docker Personal: |
   Docker Personal is a [Docker subscription](#docker-subscription). With its focus on the open-source communities, individual developers, education, and small businesses, Docker Personal will continue to allow free use of Docker components - including the Docker CLI, Docker Compose, Docker Engine, Docker Desktop, Docker Hub, Kubernetes, Docker Build and Docker BuildKit, Docker Official Images, Docker Scan, and more.
 Docker Pro: |
@@ -108,7 +110,7 @@ Docker subscription: |
 Docker Team: |
   Docker Team is a [Docker subscription](#docker-subscription). Docker Team offers capabilities for collaboration, productivity, and security across organizations. It enables groups of developers to unlock the full power of collaboration and sharing combined with essential security features and team management capabilities.
 Docker Trusted Content Program: |
-  The Docker Trusted Content Program verifies content through four programs, [Docker Official Images](#docker-official-images), [Docker Verified Publisher Images](#docker-verified-publisher-images), Docker Open Source Images, and Custom Official Images.
+  The Docker Trusted Content Program verifies content through four programs, [Docker Official Images](#docker-official-images), [Docker Verified Publisher Images](#docker-verified-publisher-images), [Docker Open Source Images](#docker-open-source-images), and Custom Official Images.
 Docker Verified Publisher Images: |
   Docker Verified Publisher Images are confirmed by Docker to be from a trusted software publishers that are partners in the Verified Publisher program. Docker Verified Publisher Images are identified by the Verified Publisher badge included on the Docker Hub repositories.
 Dockerfile: |
@@ -172,7 +174,7 @@ libcontainer: |
 libnetwork: |
   libnetwork provides a native Go implementation for creating and managing container network namespaces and other network resources. It manages the networking lifecycle of the container performing additional operations after the container is created.
 member: |
-  The people who have recieved and accepted invitations to join an [organization](#organization).
+  The people who have received and accepted invitations to join an [organization](#organization). Member can also refer to members of a [team](#team) within an organization.
 namespace: |
   A [Linux namespace](https://man7.org/linux/man-pages/man7/namespaces.7.html)
   is a Linux kernel feature that isolates and virtualizes system resources. Processes which are restricted to a namespace can only interact with resources or processes that are part of the same namespace. Namespaces
@@ -187,7 +189,7 @@ node: |
 organization: |
   An organization is a collection of teams and repositories that can be managed together. Docker users become members of an organization when they are assigned to at least one team in the organization.
 organization name: |
-  The organization name, sometimes referred to as the Organization Namespace or the Org ID, is the unique identifier of a Docker organization.
+  The organization name, sometimes referred to as the organization namespace or the org ID, is the unique identifier of a Docker organization.
 overlay network driver: |
   Overlay network driver provides out of the box multi-host network connectivity
   for Docker containers in a cluster.
@@ -220,7 +222,7 @@ SSH: |
   SSH (secure shell) is a secure protocol for accessing remote machines and applications.
   It provides authentication and encrypts data communication over insecure networks such as the Internet. SSH uses public/private key pairs to authenticate logins.
 seats: |
-  The number of seats refers to the number of planned users within an [organization](#organization).
+  The number of seats refers to the number of planned members within an [organization](#organization).
 service: |
   A [service](/engine/swarm/how-swarm-mode-works/services/) is the definition of how you want to run your application containers in a swarm. At the most basic level, a service  defines which container image to run in the swarm and which commands to run in the container. For orchestration purposes, the service defines the "desired state", meaning how many containers to run as tasks and constraints for deploying the containers.
 

docker-hub/onboarding-faqs.md

@@ -11,7 +11,7 @@ services. All you need is an email address to create a Docker ID. Your Docker ID
 numbers and lowercase letters. You cannot use any special characters or spaces.
 For more information, see [Docker ID](../docker-id/index.md). If your admin enforces [Single sign-on (SSO)](../single-sign-on/index.md), a Docker ID is provisioned for new users.
 
-Developers may have multiple Docker IDs in order to separate their Docker IDs  that are associated with an organization in Docker Business, and their personal use Docker IDs. 
+Developers may have multiple Docker IDs in order to separate their Docker IDs that are associated with an organization in Docker Business or Team, and their personal use Docker IDs.
 
 ### What if my Docker ID is taken?
 
@@ -33,6 +33,10 @@ manage users, teams, and repositories in the organization. [Learn more](orgs.md)
 
 To begin, you should set up your first organization and contact the Customer Success team at customer-success@docker.com to add the additional organizations. Also, if you are enabling SSO, it is configured based on your domain, not your organization.
 
+### What's an organization name or namespace?
+
+The organization name, sometimes referred to as the organization namespace or the org ID, is the unique identifier of a Docker organization. The organization name cannot be the same as an existing Docker ID.
+
 ### What’s a team?
 
 A **Team** is a group of Docker users that belong to an organization. An organization can have multiple teams. When you first create an organization, you’ll see that you have a team, the owners team, with a single member. An organization owner can then create new teams and add members to an existing team using Docker IDs or email address and by selecting a team the user should be part of. [Learn more](orgs.md#create-a-team).
@@ -64,6 +68,13 @@ select the **Owners** team from the drop-down menu. [Learn more](orgs.md#the-own
 
 No. Organization owners can invite users through email and also choose a team for them to join within the invite.
 
+### Can I force my organization's members to authenticate before using Docker Desktop and are there any benefits?
+
+Yes. You can [enforce sign in](../docker-hub/configure-sign-in.md) and some benefits are:
+
+- Administrators can enforce features like [Image Access Management](../docker-hub/image-access-management.md) and [Registry Access Management](../docker-hub/registry-access-management.md).
+ - Administrators can ensure compliance by blocking Docker Desktop usage for users who do not sign in as members of the organization.
+
 ### If a user has their personal email associated with a user account in Docker Hub, do they have to convert to using the org’s domain before they can be invited to join an organization?
 
 Yes. When SSO is enabled for your organization, each user must sign in with the company’s domain. However, the user can retain their personal credentials and create a new Docker ID associated with their organization's domain.
@@ -95,6 +106,17 @@ owners can manage the list of invitees through the **Invitees** tab on the organ
 
 Yes. Organization owners will take up a seat.
 
+### What is the difference between user, invitee, seat, and member?
+
+User may refer to a Docker user with a Docker ID.
+
+An invitee is a user who has been invited to join an organization, but has not yet accepted their invitation.
+
+Seats is the number of planned members within an organization.
+
+Member may refer to a user that has received and accepted an invitation to join an organization. Member can also refer to a member of a team within an organization.
+
+
 ### If there are two organizations and a user belongs to both orgs, do they take up two seats?
 
 Yes. In a scenario where a user belongs to two orgs, they take up one seat in each organization.
@@ -111,3 +133,15 @@ organization. [Learn more](orgs.md#configure-repository-permissions).
 
 Docker SSO allows only one IdP configuration per organization. For more
 information, see [Configure SSO](../single-sign-on/index.md) and [SSO FAQs](../single-sign-on/faqs.md).
+
+### What is a service account?
+
+A [service account](../docker-hub/service-accounts.md) is a Docker ID used for automated management of container images or containerized applications. Service accounts are typically used in automated workflows, and do not share Docker IDs with the members in the Team or Business plan. Common use cases for service accounts include mirroring content on Docker Hub, or tying in image pulls from your CI/CD process.
+
+### Does my organization need to use Docker's registry?
+
+A registry is a hosted service containing repositories of images that responds to the Registry API. Docker Hub is Docker's primary registry, but you can use Docker with other container image registries. You can access the default registry by browsing to [Docker Hub](https://hub.docker.com) or using the `docker search` command.
+
+### What is included in my Docker Business or Team plan?
+
+For a list of features available in each tier, see [Docker subscription overview](../subscription/index.md).