Repo sync

data/reusables/billing/enhanced-billing-platform-product.md

@@ -12,7 +12,7 @@ Beginning in February 2025, {% data variables.product.company_short %} will migr
 
 <!-- end expires 2025-04-30 -->
 
-For existing personal accounts created before February 13, 2025, {% data variables.product.company_short %} will migrate personal accounts to the new billing platform in the future. You will receive a notice 30 days before migration.
+For existing personal accounts created before February 13, 2025, {% data variables.product.company_short %} will migrate personal accounts to the new billing platform by June 30, 2025.
 
 {% elsif ghec %}
 

data/reusables/repositories/rulesets-commit-regex.md

@@ -6,8 +6,6 @@ Rulesets support RE2 syntax. For more information, see Google's [syntax guide](h
 
 By default, regular expressions in metadata restrictions do not consider multiple lines of text. For example, if you have a multiline commit message, the pattern `^ABC` will be a match if the first line of the message starts with `ABC`. To match multiple lines of the message, start your expression with `(?m)`.
 
-When using regular expression metacharacter classes that contain a backslash `\` it must be escaped with an additional backslash. For example `task#\\d{1,4}`
-
 The negative lookahead assertion, denoted `?!`, is not supported. However, for cases where you need to look for a given string that is not followed by another given string, you can use the positive lookahead assertion, denoted `?`, combined with the "Must not match a given regex pattern" requirement.
 
 > [!NOTE]