Update available messaging for domain availability search component on home page

[gabo0oo]

Issue description

We need to update the "This domain is available!" messaging on the get.gov home page domain search section to align with the message that appears on the .gov domain step of the domain request form. As a general rule, we want to say that while a domain might be available, that does not guarantee a requestor can get that domain. Let's be clear across all our messaging.

On the home page we say:

That domain is available! Read about next steps to take before requesting your .gov domain.

On the Choosing your .gov domain page under the Domains section we say:

That domain is available!

We’ll try to give you the domain you want, but it’s not guaranteed.
Read about next steps to take before requesting your .gov domain.

Acceptance criteria

• On the Choosing your .gov domain page under the Domains section match the exact copy and styling as the available message on the home page
• On the home page change the hatch mark (') to a apostrophe (’) on "We'll" in the

  under "Start your .gov domain search"

Note that there is a ticket in the registrar repo that covers some of this AC. cisagov/manage.get.gov#1698

Additional context

See this Slack thread with Cameron's comments

Links to other issues

No response

[katypies]

Our messaging when a domain isn't available is also inconsistent (on the homepage, we refer to the Domains page, where you have to search again, and then we point you to the WHOIS/RDAP lookup). If we're updating the homepage component, it might make sense to ensure that those messages are also consistent. Added refinement so we can determine if this should be two related tickets or put together for standardizing them.

[allly-b]

@gabydisarli should we ever use the hatch mark? I did a search and we have 11 cases where we are using a hatchmark in get.gov instead of an apostrophe. We have 20+ on the manage.get.gov repo (including in email templates). This would be a quick houskeeping ticket (one for each repo) if we just want to change to apostrophe across the board.

[katypies]

I'm guessing that using the rich-text apostrophe across get.gov is fine, but we should be aware of whether it gets encoded instead of displayed/processed as expected (similar to cisagov/manage.get.gov#1549).

[gabo0oo]

@abroddrick any way we can automate this would be amazing. They keep cropping up. I don't think there will ever be a use case where we will need to use a hatch mark unless we'll be referring to feet (the measurement).