adding git commit info

website/docs/docs/cloud/dbt-cloud-ide/git-commit-signing.md

@@ -6,9 +6,9 @@ sidebar_label: Git commit signing
 
 # Git commit signing <Lifecycle status="Enterprise" />
 
-To improve identity protection/impersonation and enhance security, you can sign your Git commits when pushing them to the repository. Using your signature, a Git provider can cryptographically verify it and mark the commit as "verified", giving people increased confidence about the origin of the commit. 
+To prevent impersonation and enhance security, you can sign your Git commits when pushing them to the repository. Using your signature, a Git provider can cryptographically verify it and mark the commit as "verified", giving people increased confidence about the origin of the commit.
 
-You can configure dbt Cloud to sign your Git commits when using the IDE for development. To set up, enable the feature in dbt Cloud, generate a GPG keypair, and upload the public key to your Git provider to use for signature verification.  
+You can configure dbt Cloud to sign your Git commits when using the IDE for development. To set up, enable the feature in dbt Cloud, follow the flow to generate a keypair, and upload the public key to your Git provider to use for signature verification.  
 
 
 ## Prerequisites 
@@ -59,6 +59,7 @@ If you delete your GPG keypair in dbt Cloud, your Git commits will no longer be
 
 <DetailsToggle alt_header="What if my Git provider doesn't support GPG keys?">
 
-Currently, GitHub or GitLab are supported Git providers for git commit signing (Azure DevOps is not supported). If your Git provider doesn't support GPG keys, you won't be able to sign your Git commits. You can still commit code to your repository, but the commits won't be marked as "verified".
+GitHub or GitLab are supported Git providers for git commit signing (Azure DevOps is not supported). If your git provider requires commit verification, unsigned or unverified commits might be rejected. You can configure commit verification requirements in your git provider. If your git provider doesn't enforce commit verification and doesn't support GPG keys, then you can commit but your commits will be marked unverified because there’s no GPG key available to verify them.
+
 </DetailsToggle>
 

website/docs/docs/dbt-versions/release-notes.md

@@ -20,7 +20,7 @@ Release notes are grouped by month for both multi-tenant and virtual private clo
 
 ## October 2024
 
-- **New**: The dbt Cloud IDE supports signed commits for Git, available for Enterprise plans. You can sign your Git commits when pushing them to the repository to improve identity protection/impersonation and enhance security. Supported Git providers are GitHub and GitLab Refer to [Git commit signing](/docs/cloud/dbt-cloud-ide/git-commit-signing.md) for more information.
+- **New**: The dbt Cloud IDE supports signed commits for Git, available for Enterprise plans. You can sign your Git commits when pushing them to the repository to prevent impersonation and enhance security. Supported Git providers are GitHub and GitLab Refer to [Git commit signing](/docs/cloud/dbt-cloud-ide/git-commit-signing.md) for more information.
 - **New:** With dbt Mesh, you can now enable bidirectional dependencies across your projects. Previously, dbt enforced dependencies to only go in one direction. dbt checks for cycles across projects and raises errors if any are detected. For details, refer to [Cycle detection](/docs/collaborate/govern/project-dependencies#cycle-detection). There's also the [Intro to dbt Mesh](/best-practices/how-we-mesh/mesh-1-intro) guide to help you learn more best practices. 
 
 <Expandable alt_header="Coalesce 2024 announcements">