Merge pull request #502 from publiccodenet/language-improvements

Improve spelling and grammar

_posts/2023-03-27-exploring-a-world-of-open-source.md

@@ -26,10 +26,10 @@ One potential issue with the complete adoption of open source is the risk of les
 
 In terms of open-source business models, selling support and services to use the open-source software would be a possible way to sustain them. Local councils or other small public organizations that lack the in-house expertise would need to pay for support and implementation/training.
 
-However, some vendors may try to push back on making code open source due fear of losing their unique selling points, the intellectual property of particular software. One significant risk is that they would create "faux open source" where they they make the configuration so complex and advanced that the codebase is too generic to be useful, thus preserving their "secret sauce". Standardization and protocols could help mitigate this issue, with open standards encouraged by open source software as the baseline.
+However, some vendors may try to push back on making code open source due fear of losing their unique selling points, the intellectual property of particular software. One significant risk is that they would create "faux open source" where they make the configuration so complex and advanced that the codebase is too generic to be useful, thus preserving their "secret sauce". Standardization and protocols could help mitigate this issue, with open standards encouraged by open source software as the baseline.
 
-Finally, the knock-on effect of a "right to repair" style movement for public purpose open source software could lead to job creation, increased labour mobility and economic growth.
+Finally, the knock-on effect of a "right to repair" style movement for public purpose open source software could lead to job creation, increased labor mobility and economic growth.
 
-It was an interesting experience facilitating this session, as the premise for it is so far beyond the current situation that many participants struggled to stick to this and fell back into discussing current problems. However, it still gave some new thoughts for us and specifically the risk of homogenization through codebases having a huge "market share" was something that I personally hadn't reflected on before. To me, the built-in possibility for local adaptation of open source software has always been a safeguard for this, but as was pointed out, many small organizations may not have the capabilities do do that and will just use the cheapest tool available, wether it is open source or proprietary.
+It was an interesting experience facilitating this session, as the premise for it is so far beyond the current situation that many participants struggled to stick to this and fell back into discussing current problems. However, it still gave some new thoughts for us and specifically the risk of homogenization through codebases having a huge "market share" was something that I, personally, hadn't reflected on before. To me, the built-in possibility for local adaptation of open source software has always been a safeguard for this, but as was pointed out, many small organizations may not have the capabilities to do that and will just use the cheapest tool available, whether it is open source or proprietary.
 
 I also found the reflection of the importance of open standards alongside open source to be a good reminder, and am happy that we already have it as a criterion in the [Standard for Public Code](https://standard.publiccode.net/criteria/open-standards.html). With this early picture of the future, we can steer towards the good parts and away from the not-so-good ones and perhaps one day reach this utopia.