/pricing fix, plus action link and edit to what the 70p is for on lan…

[emmagifford]

…ding page

Description

This PR includes:

• new action link to /pricing in the pricing section of the landing page - thanks Jake for figuring out how to do this!
• fix to the inaccurate, old 65p letter price on the main /pricing parent page
• changing 'standard postage' to 'accessible formats included' in the card on the landing page, to clarify that it's not the price for standard formats, and that accessible formats are already factored into this price
• updating some content on /pricing/letters to highlight that the standard cost of postage is actually 65p but we charge more due to it being a blended rate - also needed to remove the bit about it being 70p for a single double-sided sheet as technically there'll be an allowance for some users to send more sheets at the same price

Context

The /pricing parent page change is just to fix an inaccuracy.

The landing page and /pricing/letters changes come as a result of Joe Gamble's concerns that our pricing could be perceived as too high compared to competitors. Joe initially wanted to include the 65p point on the landing page but we were able to persuade him against this as it could be misinterpreted and leave us open to challenge.

Joe felt strongly that we needed to include the 65p sentence in the other page as he needs a figure to be able to point potential users to. He wants to show what the standard format part of the price so users can compare that more easily.

Joe was happy with the compromise to change the card text and add the new action link to encourage users to read more about our pricing.

Type of changes

• Refactoring (non-breaking change)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would change existing functionality)
• Bug fix (non-breaking change which fixes an issue)

Checklist

• I am familiar with the contributing guidelines
• I have followed the code style of the project
• I have added tests to cover my changes
• I have updated the documentation accordingly
• This PR is a result of pair or mob programming

---

Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.

• I confirm that neither PII/PID nor sensitive data are included in this PR and the codebase changes.

[jakecosgrove]

All good here! 🙌