Change language on View-only Dashboard Access screen

Feature Description

Bug bash issue: https://app.asana.com/0/1202258919887896/1202444327251138 please see Asana for background

Current language under the header is “Get insights about how people find and use your site, how to improve and monetize your content, directly in your WordPress dashboard” which is not a complete sentence.

Change to: “Get insights about how people find and use your site as well as how to improve and monetize your content, directly in your WordPress dashboard”

---

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

• The string in SetupUsingProxyViewOnly.js should be changed from
  “Get insights about how people find and use your site, how to improve and monetize your content, directly in your WordPress dashboard” to:

  Get insights about how people find and use your site as well as how to improve and monetize your content, directly in your WordPress dashboard.

Implementation Brief

• Change string at https://github.com/google/site-kit-wp/blob/908caf36d82feb6b7133ce2604a32d591242d2eb/assets/js/components/setup/SetupUsingProxyViewOnly.js#L108 to “Get insights about how people find and use your site as well as how to improve and monetize your content, directly in your WordPress dashboard”

Test Coverage

• No new tests needed.

QA Brief

• Navigate to the header in the view only dashboard access screen.
• The text should read:

“Get insights about how people find and use your site as well as how to improve and monetize your content, directly in your WordPress dashboard.”

instead of:

“Get insights about how people find and use your site, how to improve and monetize your content, directly in your WordPress dashboard”

Changelog entry

• Update the text on the view-only splash screen.

[aaemnnosttv]

Let’s fix it, it should be a very quick fix. We just need to remove the googlesitekit-setup__description on the second paragraph.

[eclarke1]

I agree to having a space in between those 2 paragraphs, wonder if @marrrmarrr can also comment to this. I notice this is in Approval though, so might be worth keeping it in the QA column until that decision is made. Moving it back there now. @marrrmarrr let us know if you agree to adding a space between those 2 paragraphs please.