#7893634 Fix/74148 update copies for woo commerce

Related to #74148, woo commerce

Proposed Changes

Change the heading from Get started in minutes to Let’s get started.

Change the description from First, let’s create your account. Already registered? Log in to All Woo stores are powered by WordPress.com. Please create an account to continue. Already registered? Log in.

Change the heading from Get started in minutes to Let’s get started.

Change the description from First, log in with your WordPress.com account. Don’t have an account? Sign up to All Woo stores are powered by WordPress.com! First, select the account you’d like to use.

Change the description from First, select the account you’d like to use. to All Woo stores are powered by WordPress.com! Please, log in to continue. Don’t have an account? Sign up.
*

Testing Instructions

1. Log in WP account and log out WC account
2. Go to woocommerce.com
3. Click on “Get Started”
4. Replace the host with Calypso Live or your local Calypso host
5. Confirm the changes are as described in the #74148

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• Have you written new tests for your changes?
• Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
• Have you checked for TypeScript, React or other console errors?
• Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
• Have we added the “[Status] String Freeze” label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
• For changes affecting Jetpack: Have we added the “[Status] Needs Privacy Updates” label if this pull request changes what data or activity we track or use (p4TIVU-ajp-p2)?