<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "bug" label: - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary <!-- Summarize the bug encountered concisely. --> When a project as no associated compliance framework, the copy indicates creating one using GraphQL.  Given the user can now create and associate compliance framework from the UI, we need not specify the workflow of creating via GraphQL. Please note that the GraphQL apis are available to create frameworks. ### Steps to reproduce <!-- Describe how one can reproduce the issue - this is very important. Please use an ordered list. --> 1. Create a group, and a project within the group 2. Upgrade Group / Instance to at least Premium tier 3. Navigate to any one of the project within the group 4. Go to 'Compliance Framework' section (`project` < `General` < `Compliance framework`) ### What is the expected *correct* behavior? <!-- Describe what you should see instead. --> Update text to (_pending review_): No compliance frameworks are in use. Create one from the [Compliance frameworks](https://docs.gitlab.com/ee/user/project/settings/#custom-compliance-frameworks) section in Group Settings