Proposed changes

This PR proposes two minor documentation updates to reflect recent changes regarding the use ofpurgeCSSPlugin. Additionally, it addresses any potential oversights wherepurgecss was still referenced instead ofpurgeCSSPlugin.

The modification todocs/getting-started.md appeared straightforward, especially when compared to similar changes we've made in the past. Specifically, we're not utilizing the imported item in this case.

For the update topackages/postcss-purgecss/README.md, I tested the approach locally. However, since I'm not an advanced user of PurgeCSS, there may be nuances I've missed, so I'm open to feedback on this part.

Types of changes

What types of changes does your code introduce?
Put anx in the boxes that apply

• Documentation fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

Put anx in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• Lint and unit tests pass locally with my changes

  • Note: there was a linting issue but apparently not linked to my modifications since I replicate in themainbranch

  /Users/ju/purgecss/docs/.vuepress/.cache/deps/@vue_devtools-api.js3901:5  error  Definitionfor rule'es5/no-es6-methods' was not found  es5/no-es6-methods

• (N/A) I have added tests that prove my fix is effective or that my feature works

• I have added necessary documentation (if appropriate)

Further comments

N/A