Adjust pricing page popups take3

<!--

This template is for requesting work to an existing webpage  [marketing website](https://about.gitlab.com/) , or logged out gitlab.com.

DO NOT use this for:
New webpages, docs.gitlab.com, the GitLab product (In app), the handbook or other items.

For information regarding working on the about website please visit the [Brand and Digital Handbook](https://about.gitlab.com/handbook/marketing/growth-marketing/brand-and-digital-design/#digital-team)

TITLE THIS ISSUE: Page Update: [Your Relevant Title]
-->
## Overview

This is related to https://gitlab.com/gitlab-com/marketing/growth-marketing/brand-and-digital/brand-and-digital/-/issues/212#note_389216039

#### Briefly describe your request
What is going to be added/removed, etc.
<!--
Example: Update existing information. Some examples of this are for changes in direction, programs, partnerships, or annual updates.
-->

`Add more style emphasis to the links, continuing work from` https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/8584

#### Describe why this update is being requested:
What problem(s) are you trying to solve? What are the goals?

<!--
Examples:
* Users can't find what they're looking for.
-->

* `Users would like a quick look "does this tier have the features I need for a specific category/topic?"`
* `The quicker a user sees what they want, the more likely they are to buy.`

#### What is/are the relevant URL(s)
`https://about.gitlab.com/pricing/`
<!--
Example: https://about.gitlab.com/etc/
-->
_________

## Project Management

#### What is the due date AND WHY? Dates without reason are difficult to prioritize. If there is no due date, please be as specific as possible about a timeframe and need.
`2020-08-13. We're reusing code but adding some CSS so it should be quick.`
<!--
Please note: Without sufficient lead time we will likely be unable to meet your deadline. Marketing web development is currently an impacted resource.

Example: Our due date is XXXX-XX-XX. We want to launch this page before a trade show happens on YYYY-YY-YY. We need a week of lead time to coordinate a press release before the event.
-->

#### Please identify the directly responsible individual (DRI), stakeholders, and roles

<!--
Who should we be asking for questions and reviews?
-->

|Name|Role|
|------|------|
| `@tbarr` | DRI |
| `@sytses` | Primary stakeholder |
| `@rreich` | Project facilitator |
| `@brandon_lyon` | Marketing developer lead for this week's MVC |
| `@shanerice` | Development partner, testing/analytics/seo, guidance/coordination | 
| `@skarpeles` | Marketing developer lead during prior iterations |
| `@jstava` | Growth group stakeholder |

 ____________

## Audience

#### Who is primarily looking at this page AND what will they they be doing with it/what do we want them to do? Write specifics AND check off below anything relevant

**Specific Details**
<!-- Write in specifics. Example: People looking for more info about devsecops", or "potential event attendees vs event sponsors. Want them to sign up for event"
-->
`Users who are ready to buy but need to know which version to purchase`

**Person**
- [x] Individual (looking for information on GitLab features, events, community, documentation)
- [x] Person representing company (looking for a solution for DevOps, getting a trial, etc)
- [ ] PR/Media
- [ ] Investors/Board members

**How much do they know about GitLab?**
- [x] Very new or first time visiting (most likely came from ads or search)
- [x] Has been here a few times 
- [ ] Very familiar (likely looking for documentation, resources, new features, community projects, etc. )

**Special Considerations (check if applicable):**

- [ ] Government
- [ ] Outside U.S. (primary)
- [ ] Direct Competitive (ex: OctoCat Campaign}

___________
## Promotion and Measurable Goals

#### What are the measurable key performance indicators (KPI)?
* `Same performance metrics currently measured on that page`
<!--
Examples:
* Email subscriptions
* Attendee signups
-->

#### Where do you expect traffic to come from?
* `The usual`
<!--
Examples:
* Organic Social media campaign
* Paid Targeted ads
-->

## Relevant Documents/Information

* [Pricing capabilities YML](https://gitlab.com/gitlab-com/marketing/growth-marketing/brand-and-digital/brand-and-digital/uploads/33772b260e9c36753dba3dc778a1b8f0/pricing_capabilities.yml).
* [Related merge request with relevant code](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/58002).

## Project Deliverables

#### What are the project must-haves?

<!--
Please try to keep this list as short as possible.
Items the project cannot launch without.

(Example must-haves)
* [ ] Sign-up form
* [ ] CTA for proposals
-->

* [ ] Reusing work from the [previous iteration](https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/8584)
* [ ] Add styles to the links to attempt to improve engagement.

#### What are the project could-haves?

<!--
These are desirable but not necessary. If an opengraph is needed for social sharing please add as a COULD-HAVE deliverable.

(Example could-haves)
* Sliders
* Animations
* "Bells-and-whistles"
-->

* [ ] A/B test implemented.

## Requestor Checklist

* [x] All sections have been filled out
* [x] All media and relevant documents have been linked or added
* [x] A due date and rationale for the due date has been added
* [x] Your team labels have been added

Story points: 1.0