Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
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
3 changes: 1 addition & 2 deletions content/manuals/billing/payment-method.md
Original file line number Diff line number Diff line change
Expand Up @@ -237,8 +237,7 @@ verification email and enter the amount of this deposit to verify your account.

## Failed payments

You can't manually retry a failed payment. Docker will retry failed payments
based on the retry schedule.
If your payment fails, you can select **Pay now**, which redirects you from Docker Hub to the invoice in Stripe. You can then manually retry the payment through Stripe.

If your subscription payment fails, there is a grace period of 15 days,
including the due date. Docker retries to collect the payment 3 times using the
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,10 @@

## What happens if my existing certificate expires?

If your certificate expires, contact your identity provider to retrieve a new X.509 certificate. Then update the certificate in the [SSO configuration settings](/manuals/enterprise/security/single-sign-on/manage.md#manage-sso-connections) in the Docker Admin Console.
Docker recommends that you contact your identity provider to retrieve a new X.509 certificate, then update the certificate in the [SSO configuration settings](/manuals/enterprise/security/single-sign-on/manage.md#manage-sso-connections) in the Docker Admin Console.

- If your organization doesn't enforce SSO, your users can log in with their username and password credentials.

Check warning on line 32 in content/manuals/enterprise/security/single-sign-on/FAQs/idp-faqs.md

View workflow job for this annotation

GitHub Actions / validate (vale)

[vale] reported by reviewdog 🐶 [Docker.RecommendedWords] Consider using 'sign in' instead of 'log in' Raw Output: {"message": "[Docker.RecommendedWords] Consider using 'sign in' instead of 'log in'", "location": {"path": "content/manuals/enterprise/security/single-sign-on/FAQs/idp-faqs.md", "range": {"start": {"line": 32, "column": 60}}}, "severity": "INFO"}
- If your organization enforces SSO and credentials won't work, then Docker recommends you [contact us](https://app.docker.com/support/contact) for additional support.
Copy link
Contributor

Choose a reason for hiding this comment

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

ISSUE: Awkward phrasing creates confusing logic

The phrase "If your organization enforces SSO and credentials won't work" is redundant and confusing. When SSO is enforced, credentials won't work by definition—this is the expected behavior, not a separate condition.

Suggested fix:

Break this into clearer statements:

- If your organization enforces SSO, username and password credentials won't work. Contact [Docker support](https://app.docker.com/support/contact) for additional help.

Or use parenthetical explanation:

- If your organization enforces SSO (where credentials won't work), contact [Docker support](https://app.docker.com/support/contact) for additional help.

Style note: Per STYLE.md, "Docker recommends you" is meta-commentary that adds little value. Be more direct: "Contact Docker support" instead of "Docker recommends you contact us."


## What happens if my IdP goes down when SSO is turned on?

Expand Down
Loading