.wiki/setting-up-the-paypal-gateway-v2.md (1)

3-3: Verify top‑level admin menu label used in this path.

The doc instructs users to go to “Multisite Ultimate > Settings > Payments”, but the current Dashboard_Admin_Page::get_menu_title() still returns “Multisite WaaS”. Once you finalize the menu label in code, please ensure this navigation path matches the actual label to avoid confusion.

Also applies to: 13-13

.wiki/the-registration-flow-v2.md (1)

3-3: Confirm that the documented admin paths match the actual menu label.

This article now refers to paths like “Multisite Ultimate > Settings > Login & Registration” and “Multisite Ultimate > Payments”, but the current dashboard admin class still exposes the menu title “Multisite WaaS”. Once the menu label in code is finalized, please ensure these paths match the real UI so users can follow them accurately.

Also applies to: 11-11, 47-47, 53-53

.wiki/using-wp-ultimo-mailchimp-integration.md (2)

3-3: Soften the intensifier "really" for professional tone.

The phrase "really easy" could be more professional. Consider alternatives like "straightforward" or "simple" to align with documentation standards.

-Syncing subscribers' emails with your MailChimp lists is really easy with our Multisite Ultimate: MailChimp Integration Add-on.
+Syncing subscribers' emails with your MailChimp lists is straightforward with our Multisite Ultimate: MailChimp Integration Add-on.

---

7-7: Replace "talk with" with more precise verb.

The construction "talk with the MailChimp API" is awkward. Use "communicate with," "interact with," or "connect to" instead.

-Before we start to get into the different settings available, we need a MailChimp API key. This will allow Multisite Ultimate to talk with the MailChimp API to retrieve lists, groups, and add email addresses to those lists and groups when users sign up.
+Before we start to get into the different settings available, we need a MailChimp API key. This will allow Multisite Ultimate to communicate with the MailChimp API to retrieve lists, groups, and add email addresses to those lists and groups when users sign up.

.wiki/creating-discount-codes-v2.md (1)

81-81: Consider a more idiomatic phrasing for clarity.

The phrase "To do this, go to" could be more direct and action-oriented.

Consider revising to improve readability:

-First, you need to get the shareable link for your plan. To do this, go to **Multisite Ultimate > Products** and select a plan.
+First, get the shareable link for your plan by navigating to **Multisite Ultimate > Products** and selecting a plan.

This is flagged by static analysis and makes the instruction slightly more concise.

.wiki/creating-custom-admin-pages-and-sub-pages-using-wp-ultimo-admin-page-creator.md (1)

3-3: Consider a stronger alternative to "really easy."

The static analysis tool suggests replacing the over-used intensifier "really" with a more specific or impactful descriptor to improve documentation clarity.

Example revision:

-While WordPress makes it really easy to add content to the front end of sites, creating pages and sub-pages on the admin side requires some basic coding skills. Multisite Ultimate: Admin Page Creator aims to bring that same ease of use of the front end to the back end of your network sites.
+While WordPress makes it effortless to add content to the front end of sites, creating pages and sub-pages on the admin side requires some basic coding skills. Multisite Ultimate: Admin Page Creator aims to bring that same ease of use of the front end to the back end of your network sites.

.wiki/how-do-i-install-wordpress-multisite.md (1)

65-65: Minor style improvement: prefer "can" over "able to".

As suggested by static analysis, consider using the more concise form:

-It is important to test and make sure that you are able to create a subsite on your WordPress Multisite installation before you install Multisite Ultimate.
+It is important to test and make sure that you can create a subsite on your WordPress Multisite installation before you install Multisite Ultimate.

.wiki/how-to-join-wp-ultimo-community.md (1)

7-7: Add alt text to all images for accessibility.

Multiple images throughout the documentation lack alternate text (alt text), which hinders accessibility for screen readers and SEO. The static analysis tool flagged this at line 27, and the same issue applies to all other image references.

Update each markdown image link to include descriptive alt text in square brackets:

-![](https://wp-ultimo-space.fra1.cdn.digitaloceanspaces.com/...)
+![Screenshot showing community channels interface](https://wp-ultimo-space.fra1.cdn.digitaloceanspaces.com/...)

Provide meaningful descriptions for each image (e.g., "Registration form", "Community channel list", "License unlock page", etc.).

Also applies to: 11-11, 15-15, 19-19, 23-23, 27-27, 31-31, 35-35

.wiki/site-templates-v2.md (1)

55-55: Minor style improvements for readability.

Lines 55 and 73 currently use "need to go to" and "just need to go to" respectively. Consider using more concise, direct language (e.g., "navigate to" or "go to") for a more professional tone in technical documentation.

Example improvements:

• Line 55: "To do that, go to Multisite Ultimate > Products > Edit."
• Line 73: "To configure this, go to Multisite Ultimate > Checkout Forms."

Also applies to: 73-73

.wiki/how-to-get-custom-development-help-from-codeable.md (1)

3-3: Use more formal language in documentation.

The word "awesome" is informal for professional documentation. Consider replacing it with a more formal alternative such as "significant" or "valuable."

Apply this diff to improve language formality:

-Sometimes, we really need some awesome customization to make our network flows exactly the way we want. If that's what you are looking for, we recommend [Codeable](https://codeable.io/partners/wpultimo/?ref=7wHwE), a place where you can find experienced developers with Multisite Ultimate expertise.
+Sometimes, we really need significant customization to make our network flows exactly the way we want. If that's what you are looking for, we recommend [Codeable](https://codeable.io/partners/wpultimo/?ref=7wHwE), a place where you can find experienced developers with Multisite Ultimate expertise.

.wiki/what-is-wordpress-multisite.md (1)

59-59: Concise the verbose phrasing in the note.

The branding change is correct, but the sentence can be more concise by replacing "In order to allow" with "To allow".

-_Note: as you can see, inviting someone to your network and granting them super admin status gives this user total control over your network. As an example, other super admins can even remove your super admin status, effectively locking you out of your own network admin panel. In order to allow Multisite Ultimate customers to have granular control over what additional super admins can do, we have an add-on called Support Agents. This add-on allows you to create yet another kind of user – an agent – with only the permissions they might need to perform their tasks on the network._
+_Note: as you can see, inviting someone to your network and granting them super admin status gives this user total control over your network. As an example, other super admins can even remove your super admin status, effectively locking you out of your own network admin panel. To allow Multisite Ultimate customers to have granular control over what additional super admins can do, we have an add-on called Support Agents. This add-on allows you to create yet another kind of user – an agent – with only the permissions they might need to perform their tasks on the network._

.wiki/tax-handling.md (1)

11-11: Reduce repetitive phrasing for clarity.

The phrase "you need to go" is already used in line 11. Consider rewording for variety: "To enable it, navigate to Multisite Ultimate > Settings > Taxes and toggle the Enable Taxes setting." or similar.

.wiki/basic-concepts.md (1)

3-3: Improve conciseness in two passages per static analysis hints.

Static analysis suggests two minor wordiness improvements:

1. Line 3: "a lot of new words and phrases to take on board" — consider using more concise phrasing such as "many new terms and concepts to learn."
2. Line 103: "especially if used in conjunction with services" — consider replacing "in conjunction with" with simply "with" for brevity.

These are minor improvements for readability.

Apply this diff for optional refinements:

-For a new WordPress Multisite user and someone who just started using Multisite Ultimate, there can be a lot of new words and phrases to take on board at first.
+For a new WordPress Multisite user and someone who just started using Multisite Ultimate, there can be many new words and phrases to learn at first.

-[Multisite Ultimate webhooks](https://help.wpultimo.com/article/337-integrating-wp-ultimo-with-zapier-using-webhooks) open infinite possibilities, allowing network admins to do all sorts of crazy-but-useful integrations, especially if used in conjunction with services like _Zapier and IFTTT_.
+[Multisite Ultimate webhooks](https://help.wpultimo.com/article/337-integrating-wp-ultimo-with-zapier-using-webhooks) open infinite possibilities, allowing network admins to do all sorts of crazy-but-useful integrations, especially if used with services like _Zapier and IFTTT_.

Also applies to: 103-103

.wiki/using-wp-ultimo-affiliatewp-integration-to-create-your-own-referral-program-for-wp-ultimo.md (2)

5-7: Remove redundant phrase for clarity.

The phrase "First of all" is redundant. Remove it to make the guidance more concise.

Apply this diff:

-First of all, you **need to have** [**AffiliateWP**]
+You **need to have** [**AffiliateWP**]

---

17-17: Remove emphasis formatting from image caption.

This line functions as an image caption but is incorrectly formatted with emphasis (_). Remove the emphasis marks to treat it as plain explanatory text, which is more semantically appropriate for a caption.

Apply this diff:

-_Check the Multisite Ultimate box at the bottom and save_
+Check the Multisite Ultimate box at the bottom and save

inc/admin-pages/class-about-admin-page.php (1)

98-101: Menu label text still uses old “Multisite WaaS” name

The textdomain is updated, but the visible label string still says “Multisite WaaS”. If the public branding is now “Multisite Ultimate”, consider updating the label:

-        return __('Multisite WaaS', 'multisite-ultimate');
+        return __('Multisite Ultimate', 'multisite-ultimate');

inc/admin-pages/class-broadcast-list-admin-page.php (2)

179-179: Optional: improve pluralization for customer count

The string __('%s customer(s) targeted.', 'multisite-ultimate') works but isn’t ideal for i18n plural rules. Consider _n() to give translators proper singular/plural forms:

- $description = sprintf(__('%s customer(s) targeted.', 'multisite-ultimate'), $customer_count);
+ $description = sprintf(
+   _n('%s customer targeted.', '%s customers targeted.', $customer_count, 'multisite-ultimate'),
+   $customer_count
+ );

---

265-428: Modal field textdomain updates look consistent; minor copy nit

All field titles, descriptions, tooltips, placeholders, and button labels in the broadcast modal correctly switched to the multisite-ultimate textdomain with no logic changes, which keeps behavior intact and aligns with the rebranding.

One small copy nit you may want to fix while you’re here:

• Line 324: “Search for a product..” has a double period. Consider changing to a single period:

- 'placeholder'       => __('Search for a product..', 'multisite-ultimate'),
+ 'placeholder'       => __('Search for a product.', 'multisite-ultimate'),

.wiki/why-is-wp-ultimo-no-longer-sold-at-codecanyon.md (2)

9-9: Consider reducing exclamation marks for a more professional tone.

The paragraph contains five exclamation marks, which may seem excessive for this context. Reducing them slightly would improve readability and professionalism.

Suggested revision:

-**OMG! I bought a license on CodeCanyon! What will happen to me?**
+**I bought a license on CodeCanyon. What will happen to me?**

Or alternatively, keeping some enthusiasm:

-**OMG! I bought a license on CodeCanyon! What will happen to me?**
+**I bought a license on CodeCanyon — what happens next?**

---

11-11: Consider a more concise phrasing.

"in order to avoid purchases there" can be more concise. The current phrasing is slightly awkward.

Suggested fix:

-You will find Multisite Ultimate on the platform though, at an unusually high price, in order to avoid purchases there. The product will not be removed from CodeCanyon until the transition process is fully completed.
+You will find Multisite Ultimate on CodeCanyon at an unusually high price to discourage purchases there. The product will not be removed until the transition is complete.

inc/admin-pages/class-broadcast-edit-admin-page.php (3)

360-360: Product targets description and loading text – consider pluralization improvement

The domain changes to multisite-ultimate for both '%s customer(s) targeted.' and 'Loading...' are correct.

If you touch this again, consider using _n() for proper pluralization, e.g.:

$description = sprintf(
    _n(
        '%s customer targeted.',
        '%s customers targeted.',
        $customer_count,
        'multisite-ultimate'
    ),
    $customer_count
);

This will give better i18n support for singular/plural forms.

Also applies to: 374-374

---

390-390: Page title and menu title strings OK; capitalization tweak optional

Both get_title() and get_menu_title() now correctly use the multisite-ultimate domain. If you want to align with common WordPress UI copy, you could optionally change 'Add new Broadcast' to 'Add New Broadcast' for consistent capitalization with core screens.

Also applies to: 401-401

---

423-433: Labels array textdomain migration looks good; minor copy polish optional

All labels (edit_label, add_new_label, updated_message, etc.) are correctly switched to multisite-ultimate and use __() in the right context.

If you care about English copy polish, you might later change:

• 'Broadcast updated with success!' → 'Broadcast updated successfully.'

but that’s stylistic and not required for functionality.

.wiki/re-ordering-the-wp-ultimo-country-list.md (1)

1-21: Confirm whether wp-ultimo text domain is still correct

The heading branding update to “Multisite Ultimate” is fine. However, the example still uses the wp-ultimo text domain:

$countries = array_merge(array( 'DE' => __('Germany', 'wp-ultimo'), ), $countries);

If the plugin’s actual text domain has been changed to something else in this PR (e.g., multisite-ultimate), this snippet should be updated for consistency; if the runtime domain is still wp-ultimo, leaving it as-is is correct.

.wiki/managing-shareable-links-for-plans.md (1)

3-3: Copy is correct; optional minor tightening

The new branding reference is correct. For slightly tighter prose you could change:

“In order to do this, go to any of your plans' edit pages…”

to:

“To do this, go to any of your plans’ edit pages…”

Totally optional.

.wiki/setting-up-manual-payments-v2.md (1)

3-12: Branding/path look good; consider fixing nearby grammar

• Line 3 correctly reflects “Multisite Ultimate version 2.x”.
• Line 11’s “Multisite Ultimate > Settings > Payments” path is clear and aligned with the new name.

While you’re touching this section, you might want to fix the existing sentence on line 5:

“Manual payments are a way for to you offer other payment methods should Stripe or PayPal is not available…”

Suggested rewrite:

“Manual payments let you offer other payment methods when Stripe or PayPal is not available for your users.”

Optional, but improves readability.

inc/admin-pages/class-base-admin-page.php (1)

7-8: Base admin page branding/text-domain updates are safe

The references to “Multisite Ultimate” in docblocks and branding helpers (add_branding, brand_header, brand_footer) are consistent, and the documentation title link now uses the multisite-ultimate text domain. Runtime behavior of menu/page registration and hooks is unchanged; just ensure your translation catalog includes the updated 'Documentation' string under the new domain.

Also applies to: 199-199, 475-476, 512-513, 528-529, 602-603, 629-630

data/translatable-strings.php (1)

13-20: Time-unit translatable strings correctly moved to new text domain

The entries for day/days, week/weeks, month/months, and year/years now use the multisite-ultimate domain while preserving keys and source text. This matches the broader i18n migration in the PR; just ensure your .po/.mo files are regenerated for the new domain.

.wiki/how-to-configure-domain-mapping-v2.md (1)

3-6: Domain mapping doc branding is correct; consider minor wording/markdown polish

The updates correctly rebrand the feature to Multisite Ultimate and adjust paths like Multisite Ultimate > Settings > Domain Mapping, Multisite Ultimate > Domains, and Multisite Ultimate > Products, which keeps the instructions in sync with the new UI.

A few optional cleanups while you’re here:

• In “Multisite Ultimate will check if the domain has SSL or not…”, consider “check whether the domain has SSL or not” for smoother wording.
• The provider list uses mixed capitalization: Runcloud, Gridpane, Cpanel. You may want to standardize these to the vendors’ preferred names (e.g., “RunCloud”, “GridPane”, “cPanel”) for a more polished doc.
• Several images are included as ![](…) with no alt text; adding brief alt text would improve accessibility and satisfy MD045.
• The intro line uses “see**_ this article .”; removing the extra space between the emphasized text and the link bracket will address the MD039 “spaces inside link text” warning.

None of these affect behavior but would tighten up the documentation quality.

Also applies to: 9-16, 19-24, 45-46, 55-56, 77-78, 85-86, 95-96, 115-120

.wiki/touring-the-admin-panel.md (1)

15-83: Add descriptive alt text for images to improve accessibility.

All screenshots use empty alt text (![](…)), which triggers MD045 and makes the content less accessible. Consider adding short, meaningful alt text (e.g., “Screenshot of the Multisite Ultimate Dashboard”) for each image.

.wiki/editing-plugins-and-themes-meta-information-with-wp-ultimo-plugin-and-theme-manager.md (2)

15-15: Add alt text to image for accessibility.

Line 15 is missing alt text. Update the markdown to include descriptive alt text for better accessibility.

-![](https://wp-ultimo-space.fra1.cdn.digitaloceanspaces.com/hs-file-4zDOF0uomh.png)
+![Global options in Multisite Ultimate Plugin and Theme Manager settings](https://wp-ultimo-space.fra1.cdn.digitaloceanspaces.com/hs-file-4zDOF0uomh.png)

---

17-17: Use proper heading markdown instead of emphasis.

Line 17 uses italics for what appears to be a caption. Consider using a proper markdown heading or adjusting the formatting.

-_Here you'll find the global options added by Multisite Ultimate: Plugin and Theme Manager_
+**Note:** Here you'll find the global options added by Multisite Ultimate: Plugin and Theme Manager

.wiki/getting-started-with-the-payfast-payment-gateway.md (2)

3-3: Standardize hyphenation of "add-on" terminology.

Inconsistent usage of "addon" (line 3) and "add-on" (lines 5, 9) throughout the document. Standardize on "add-on" (with hyphen) for consistency with the rest of the documentation.

-PayFast is a leading online payment processor for businesses in South Africa. It's dedicated to helping online merchants grow by making transactions seamless and secure. As per Multisite Ultimate user's request, we decided to create an addon that will make integration with PayFast possible.
+PayFast is a leading online payment processor for businesses in South Africa. It's dedicated to helping online merchants grow by making transactions seamless and secure. As per Multisite Ultimate user's request, we decided to create an add-on that will make integration with PayFast possible.

Also applies to: 5-5, 9-9

---

35-35: Add alt text to image for accessibility.

Line 35 is missing alt text. Update the markdown to include a description of the image.

-![](https://wp-ultimo-space.fra1.cdn.digitaloceanspaces.com/hs-file-KW0WnsxHIW.png)You can simply copy and paste the credential and populate the details on your Multisite Ultimate settings.
+![PayFast account dashboard showing merchant credentials](https://wp-ultimo-space.fra1.cdn.digitaloceanspaces.com/hs-file-KW0WnsxHIW.png)
+
+You can simply copy and paste the credential and populate the details on your Multisite Ultimate settings.

.wiki/the-wp-ultimo-register-api-endpoint.md (1)

1-1: Register endpoint docs branding update is fine; consider minor Markdown cleanup

The branding changes to “Multisite Ultimate” read consistently and keep the endpoint description intact. If you want to satisfy markdownlint, you can optionally:

• Remove the leading spaces before the * bullets under “In this call, 4 processes will be executed…” so the list isn’t indented.
• Wrap the bare URL in angle brackets (e.g., <https://yoursite.com/wp-json/wu/v2/register>) or convert it to a markdown link.

These are cosmetic and not required for correctness.

Also applies to: 3-3, 9-15, 28-29, 45-45, 71-71, 82-82

.wiki/error-installing-the-sunrise-file.md (1)

5-5: Sunrise error article rebranding looks good; optional image alt‑text improvement

The references to Multisite Ultimate correctly replace the old name without changing the troubleshooting steps. For better accessibility (and to satisfy markdownlint), you may want to add descriptive alt text to the images (e.g., ![Setup wizard sunrise step screenshot](...)) instead of leaving the brackets empty.

Also applies to: 9-9, 17-17

.wiki/getting-paid-v2.md (1)

79-79: Optional: Improve writing style for formal documentation.

Line 79 uses "pretty much," which is marked as informal by style guidelines. Consider rephrasing to strengthen the documentation tone.

Suggested change: "The steps to install the GoCardless add-on are similar to the WooCommerce add-on." (Remove "pretty much the same as" and replace with "similar to")

.wiki/activating-wp-ultimo-language-selector.md (1)

5-5: Minor style improvement: Consider a synonym for "gives".

The phrase "add-ons your license gives you access to" reads slightly awkwardly. Consider using "provides" for better clarity:

-After [activating your license](1677127280-how-do-i-activate-wp-ultimo-using-my-license-key.html) you will be able to install Multisite Ultimate add-ons your license gives you access to.
+After [activating your license](1677127280-how-do-i-activate-wp-ultimo-using-my-license-key.html) you will be able to install Multisite Ultimate add-ons your license provides access to.