docs: fix typo for Browserslist in file structure guide

[MattiJarvinen]

Filename browserlist is actually browserslist

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/angular/angular/blob/master/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• angular.io application / infrastructure changes
• Other... Please describe:

What is the current behavior?

Issue Number: #28311

What is the new behavior?

Does this PR introduce a breaking change?

• Yes
• No

Other information

Documentation typo fix.

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

[MattiJarvinen]

I signed it!

[googlebot]

CLAs look good, thanks!

[brandonroberts]

Update git commit message to docs: fix typo for Browserslist in file structure guide

[MattiJarvinen]

@brandonroberts actually noticed another Browserlist mention in the file and fixed it too, also updated commit message.

[brandonroberts]

Caretaker note: This is a docs-only change and I'm using a global approval.

[MattiJarvinen]

@IgorMinar & @brandonroberts just occurred to me my CLA is with my real email address and my commit is on Github no-reply, do I have to amend it to the real address or not?

[brandonroberts]

@MattiJarvinen-BA Igor can correct me, but I believe the CLA bot uses your provided GitHub email to confirm that you've signed the CLA. So even if you just create a pull request using the pencil on any page, its still tied to the email on your GitHub account.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}