mCaptcha/website
2
0
Fork 3
Code Issues 1 Pull requests 4 Projects Releases Packages Wiki Activity

docs: Minor spelling error fixes

Browse source 
- Removal of duplicate `flexibility`.
- Fixed the `mCapthca` typo to `mCaptcha`.
- `Decenber` to `December`.
This commit is contained in:
dat-adi 2022-06-14 15:39:59 +05:30
parent d2aac837d2
commit 7b20d552e5
2 changed files with 9 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
content/blog/05-22-monthly-report/index.md
View file

@ -124,11 +124,11 @@ infrastructure of the experiment.
mCaptcha underwent a major refactor during the month of May: We re-wrote
and cleaned up all database-related stuff for higher flexibility
flexibility and generally good architecture. This refactor lays the
foundation for implementing support for alternate database software
and generally good architecture. This refactor lays the foundation
for implementing support for alternate database software
programs(we currently support PostgreSQL only).
## mCapthca is now on the Fediverse
## mCaptcha is now on the Fediverse
We recently joined the Fediverse on a
[GoToSocial](https://docs.gotosocial.org/) instance run by
@ -136,7 +136,7 @@ We recently joined the Fediverse on a
the Fediverse account.
**Fediverse account:**
[@mCapthca@batsense.net](https://gts.batsense.net/@mcaptcha)
[@mCaptcha@batsense.net](https://gts.batsense.net/@mcaptcha)
## Generic hosting
@ -151,12 +151,12 @@ adhere to the Hostea policies to operate
under the Hostea umbrella --- essentially allowing for the creation of
smaller, highly localised cooperatives.
Cooperatives are interesting, and we believe that mCapthca, too, can
Cooperatives are interesting, and we believe that mCaptcha, too, can
benefit from such an architecture as it will prevent any one party from
single-handedly sabotaging the project. The experience gained from
Hostea will be reused in providing managed hosting for mCapthca.
Hostea will be reused in providing managed hosting for mCaptcha.
By the end of this year, mCapthca will reorganise into a horizontal
By the end of this year, mCaptcha will reorganise into a horizontal
community and adopt [radical transparency](https://en.wikipedia.org/wiki/Radical_transparency#Radical_corporate_transparency) to improve trust and
reliability of the project
@ -164,7 +164,7 @@ reliability of the project
> now, so if someone is interested to help out do reach out and so that
> we could do it sooner!
In context of mCapthca, radical transparency will include all decisions
In context of mCaptcha, radical transparency will include all decisions
publicly made, funding and expenses publicly documented, and all
collaborations, too, publicly documented. This of course doesn't imply
that private, personally identifiable information(addresses and phone

2
content/blog/12-21-monthly-report/index.md
View file

@ -1,5 +1,5 @@
---
title: "Decenber, 2021: Monthly Report"
title: "December, 2021: Monthly Report"
description: "New features, improved accessibility and software
integrations"
lead: "We are mCaptcha. We build kickass CAPTCHA systems that give (DDoS) attackers a run for their money. And we do all of this without tracking your users. Oh and did I mention our UX is great?"