Fix Twitter fontawesome class in flowchart.md

[Melochaotic]

📑 Summary

Fixes a typo in fontawesome class

📏 Design Decisions

fixes simple typo - not a feature

📋 Tasks

Make sure you

• 📖 have read the contribution guidelines
• 💻 have added necessary unit/e2e tests.
• 📓 have added documentation. Make sure MERMAID_RELEASE_VERSION is used for all new features.
• 🔖 targeted develop branch

[codecov]

Codecov Report

Merging #4723 (65c9380) into develop (da602ad) will increase coverage by 6.31%.
The diff coverage is n/a.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #4723      +/-   ##
===========================================
+ Coverage    70.87%   77.18%   +6.31%     
===========================================
  Files          145      145              
  Lines        14646    14646              
  Branches       562      562              
===========================================
+ Hits         10380    11305     +925     
+ Misses        4143     3231     -912     
+ Partials       123      110      -13     

Flag	Coverage Δ
e2e	83.90% <ø> (+8.65%)	⬆️
unit	46.10% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 25 files with indirect coverage changes

[mermaid-bot]

@GingerNinjaNicko, Thank you for the contribution!
You are now eligible for a year of Premium account on MermaidChart.
# with your GitHub account to activate.

[Yokozuna59]

@sidharthv96 The PR author changed the packages/mermaid/src/docs/ without docs/.

[sidharthv96]

We have a workflow that will push the built docs to develop.

So minimal changes like this can be merged without bothering the authors.

[Yokozuna59]

Then we should do something about gh actions that will fail on each push.

[sidharthv96]

It seems like that flow is broken now.

Then we should do something about gh actions that will fail on each push.

We cannot push to forks, so we cannot update the PR branch, unless we add a PAT, which is very insecure.