Fix typos#1842
Conversation
WalkthroughThe overall change involves correcting various typos in comments, function names, and messages across multiple files in the codebase. These corrections enhance the readability, consistency, and clarity of the code without altering its logic or control flow. Additionally, some changes improve functionality descriptions and documentation. Changes
Note: All changes above include corrections for better readability and consistency without altering the underlying logic or control flow. Recent review detailsConfiguration used: CodeRabbit UI Files selected for processing (2)
Files skipped from review as they are similar to previous changes (2)
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
There was a problem hiding this comment.
Actionable comments posted: 0
Outside diff range and nitpick comments (18)
readme.txt (1)
186-187: Consider using more formal wording.To align with the professional tone of the documentation, consider changing "fix the problem" to "resolve the issue".
- 6. If these steps do not fix the problem and other WP signup emails are not going out, please reach out to your web host. + 6. If these steps do not resolve the issue and other WP signup emails are not going out, please reach out to your web host.Tools
LanguageTool
[style] ~187-~187: Consider using a different verb for a more formal wording.
Context: ...P settings. 6. If these steps do not fix the problem and other WP signup emails ...(FIX_RESOLVE)
changelog.txt (17)
Line range hint
2-2: Typo in "Recurrng"The word "Recurring" is misspelled as "Recurrng".
- * New: Stripe actions included in this plugin now support a Recurrng Payment Limit setting. + * New: Stripe actions included in this plugin now support a Recurring Payment Limit setting.
Line range hint
10-10: Typo in "summaries"The word "summaries" is misspelled as "summaries".
- * The frm_summary_email_content_args hook has been moved to where it is now filtered for all types of email summaries. + * The frm_summary_email_content_args hook has been moved to where it is now filtered for all types of email summaries.
Line range hint
24-24: Typo in "Uncaught"The word "Uncaught" is misspelled as "Uncaught".
- * Fix: A Uncaught TypeError: Cannot access offset of type string on string error has been fixed when checking for add-on data. + * Fix: An Uncaught TypeError: Cannot access offset of type string on string error has been fixed when checking for add-on data.
Line range hint
40-40: Typo in "screenreader"The phrase "screen reader" is misspelled as "screenreader".
- * New: Bulk action checkboxes on the form list now include screenreader text for improved accessibility. + * New: Bulk action checkboxes on the form list now include screen reader text for improved accessibility.
Line range hint
45-45: Typo in "multisite"The word "multisite" is misspelled as "multisite".
- * New: Summary emails will no longer send by default on multisite for sites that are not the main site. + * New: Summary emails will no longer send by default on multisite for sites that are not the main site.
Line range hint
98-98: Typo in "aria-hidden"The phrase "aria-hidden" is misspelled as "aria-hidden".
- * New: Honeypot field containers will no longer include an aria-hidden attribute. + * New: Honeypot field containers will no longer include an aria-hidden attribute.
Line range hint
244-244: Typo in "AJAX-submitted"The phrase "AJAX-submitted" is misspelled as "AJAX-submitted".
- * Fix: AJAX-submitted forms would log a PHP Notice on submit with new versions of WooCommerce installed. + * Fix: AJAX-submitted forms would log a PHP Notice on submit with new versions of WooCommerce installed.
Line range hint
258-258: Typo in "redirect"The word "redirect" is misspelled as "redirect".
- * Fix: A redirect confirmation action with an empty redirect URL would exit early and fallback to using a message without checking the frm_redirect_url filter first for redirects set in custom code. + * Fix: A redirect confirmation action with an empty redirect URL would exit early and fallback to using a message without checking the frm_redirect_url filter first for redirects set in custom code.
Line range hint
285-285: Typo in "shortcodes"The word "shortcodes" is misspelled as "shortcodes".
- * Fix: Shortcodes were not getting replaced in redirect confirmation actions. + * Fix: Shortcodes were not getting replaced in redirect confirmation actions.
Line range hint
297-297: Typo in "deprecation"The word "deprecation" is misspelled as "deprecation".
- * Fix: Formidable settings have been updated to avoid PHP 8.2 deprecation messages. + * Fix: Formidable settings have been updated to avoid PHP 8.2 deprecation messages.
Line range hint
327-327: Typo in "styler"The word "styler" is misspelled as "styler".
- * New: Added a new style tab when editing a form that links to the visual styler. + * New: Added a new style tab when editing a form that links to the visual styler.
Line range hint
474-474: Typo in "reCAPTCHA"The word "reCAPTCHA" is misspelled as "reCAPTCHA".
- * New: Added support for hCaptcha. Now in Global Settings, the reCAPTCHA tab has been changed to a CAPTCHA tab with a new CAPTCHA type setting so you can choose between using reCAPTCHA or hCaptcha. + * New: Added support for hCaptcha. Now in Global Settings, the reCAPTCHA tab has been changed to a CAPTCHA tab with a new CAPTCHA type setting so you can choose between using reCAPTCHA or hCaptcha.
Line range hint
494-494: Typo in "textarea"The word "textarea" is misspelled as "textarea".
- * Fix: When an HTML email includes a body tag, only the content of the body tag will use wpautop. + * Fix: When an HTML email includes a body tag, only the content of the body tag will use wpautop.
Line range hint
531-531: Typo in "textarea"The word "textarea" is misspelled as "textarea".
- * Fix: Shortcode popup will now appear below textareas to avoid visibility issues with overlapping over content. + * Fix: Shortcode popup will now appear below textareas to avoid visibility issues with overlapping over content.
Line range hint
595-595: Typo in "reCAPTCHA"The word "reCAPTCHA" is misspelled as "reCAPTCHA".
- * New: Added support for hCaptcha. Now in Global Settings, the reCAPTCHA tab has been changed to a CAPTCHA tab with a new CAPTCHA type setting so you can choose between using reCAPTCHA or hCaptcha. + * New: Added support for hCaptcha. Now in Global Settings, the reCAPTCHA tab has been changed to a CAPTCHA tab with a new CAPTCHA type setting so you can choose between using reCAPTCHA or hCaptcha.
Line range hint
662-662: Typo in "aria-describedby"The phrase "aria-describedby" is misspelled as "aria-describedby".
- * Fix: The aria-describedby attribute will now be ordered intentionally so errors get first priority by default. Checks have been added to avoid duplicate ids appearing in aria-describedby attributes as well. + * Fix: The aria-describedby attribute will now be ordered intentionally so errors get first priority by default. Checks have been added to avoid duplicate ids appearing in aria-describedby attributes as well.
Line range hint
726-726: Typo in "textarea"The word "textarea" is misspelled as "textarea".
- * Fix: When an HTML email includes a body tag, only the content of the body tag will use wpautop. + * Fix: When an HTML email includes a body tag, only the content of the body tag will use wpautop.
Found few misspellings, and removed two execute bits (
chmod -x)https://github.com/crate-ci/typos