summaryrefslogtreecommitdiff
path: root/doc/user/group/compliance_frameworks.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/user/group/compliance_frameworks.md')
-rw-r--r--doc/user/group/compliance_frameworks.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/user/group/compliance_frameworks.md b/doc/user/group/compliance_frameworks.md
index 0e976cec866..9f40f9e84bf 100644
--- a/doc/user/group/compliance_frameworks.md
+++ b/doc/user/group/compliance_frameworks.md
@@ -25,9 +25,9 @@ Group owners can create, edit, and delete compliance frameworks:
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/375036) in GitLab 15.6.
-Group owners can set a default compliance framework. The default framework is applied to all the new projects
-that are created within that group. It does not affect the framework applied to the existing projects. The default
-framework cannot be deleted.
+Group owners can set a default compliance framework. The default framework is applied to all the new and imported
+projects that are created within that group. It does not affect the framework applied to the existing projects. The
+default framework cannot be deleted.
A compliance framework that is set to default has a **default** label.
@@ -237,7 +237,7 @@ can be configured to be:
Generally, if a value in a compliance job:
- Is set, it cannot be changed or overridden by project-level configurations.
-- Is not set, a project-level configuration may set.
+- Is not set, a project-level configuration may be set.
Either might be wanted or not depending on your use case.