Add spellchecker

[alecslupu]

No description provided.

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

[RCheesley]

Hi there! We implemented Vale a while back, which also does spell checking. Is there a need to have another solution?

[alecslupu]

Hi there! We implemented Vale a while back, which also does spell checking. Is there a need to have another solution?

It has to do with: #159
Maybe Vale is just missing some configuration?

Apparently Vale did not caught the error, and is not catching either some others...

• the "accesible" (instead of accessible), in translations page
• the achieiving (insetad of achieving) in about page
• actvity ( instead of activity ) in participants page
• assingned in budgets page

And i could add a few more examples.

[alecslupu]

Hi there! We implemented Vale a while back, which also does spell checking. Is there a need to have another solution?

As a fun note, reading https://github.com/decidim/documentation/blob/44e3b5bd92a5e05140fa378df5f0a87966139b49/.github/actions/spelling/expect.txt

i found a few more:

• matchs
• mehod
• mesage
• propsoals
• particpant
• possiblity
• plaform
• underlied
• verfication

[RCheesley]

Hey hey! Here's a PR which fixes the Vale linter. It was silently failing (how incredibly unhelpful!)

[alecslupu]

Hey hey! Here's a PR which fixes the Vale linter. It was silently failing (how incredibly unhelpful!)

Yes, but now we still have typos in the documentation that needs to be fixed.