Merge pull request #109 from szepeviktor/typos

Fix typos

Author: alies-dev

.typos.toml

@@ -0,0 +1,12 @@
+[files]
+extend-exclude = [
+    ".git/",
+]
+ignore-hidden = false
+
+[default.extend-words]
+invokable = "invokable"
+
+[default.extend-identifiers]
+# Typos
+"Github" = "GitHub"

.vitepress/theme/style.css

@@ -109,7 +109,7 @@
 html:root {
   --vp-nav-height: 58px;
 
-  /* vp-defaut theme over-rides */
+  /* vp-default theme overrides */
   --vp-c-brand-1: var(--brand-02);
   --vp-c-brand-2: rgb(86 154 203);
 

_typos.toml

@@ -8,7 +8,7 @@ By the end of the quarter, you and your Team give each Key Result a final score,
 -   Were our OKRs aligned with the IxDF’s broader strategies?
 -   Did they keep us focused on delivering value to customers?
 -   Did we feel connected to our OKRs?
--   What have we learnt from this quarter? How do we lift the bar moving into the coming quarter?
+-   What have we learned from this quarter? How do we lift the bar moving into the coming quarter?
 
 ## Hold the Quarterly Meeting
 

guides/OKR/05-assess-your-okrs.md

@@ -218,7 +218,7 @@ function areaOfRectangle() {
 }
 ```
 
-Remember what we said: “we must make sure that Square classes are extending the Rectangle without changing their behaviour”. But, as you can see, 21 is not equal to 9.
+Remember what we said: “we must make sure that Square classes are extending the Rectangle without changing their behavior”. But, as you can see, 21 is not equal to 9.
 
 The solution would be to manage the class inheritance hierarchies correctly, for example by introducing the interface `Quadrilateral`.
 

library/backend/SOLID.md

@@ -752,7 +752,7 @@ PUT /api/users/1,id,name,444|regex:%23(.*a){100}%23
 
 ```json
 {
-    "username": "aaaaa.....ALOT_OF_REPETED_As_aaaaaaaaaa"
+    "username": "aaaaa.....ALOT_OF_REPEATED_As_aaaaaaaaaa"
 }
 ```
 

library/backend/conventions--laravel.md

@@ -62,7 +62,7 @@ everything the team does. It shows how far along they are in the sprint, as well
 
 **Issues** are tasks, design requests, new features or bugs that will be addressed in each milestone.
 
-#### Github Issue Types
+#### GitHub Issue Types
 
 -   Design Request: Design a landing page.
 -   Bug Report: Fix broken cta button.
@@ -90,7 +90,7 @@ level of priority (e.g. low, medium, high).
 
 **GitHub** as a way to manage execution of tasks (how, when, what).
 
--   Leverage Github to track progress of tasks.
+-   Leverage GitHub to track progress of tasks.
 
 ### AirTable
 
@@ -105,7 +105,7 @@ level of priority (e.g. low, medium, high).
 
 ### Slack
 
-**Slack** for communication and updates. MIRO MIRO for collaboration and ideation sessions.
+**Slack** for communication and updates. MIRO for collaboration and ideation sessions.
 
 ## Delivery Criteria
 
@@ -151,9 +151,9 @@ our [Design Principles](/outdated/design-products/design-principles.md)**?
     -   Adoption (e.g., x number of users by 21Q4)
     -   Dates (e.g., launch feature by 21Q3)
 
-### Delivery: Github
+### Delivery: GitHub
 
--   Create related Github epic with associated issues.
+-   Create related GitHub epic with associated issues.
     -   Team members assigned, requirements explained, added to milestone (See Sprint Planning Process).
     -   Insert design and/or dev issue template link here.
 

outdated/design-products/delivery-process.md

@@ -98,7 +98,7 @@ customer feedback and embracing change.
 
 -   **[What is Scrum?](https://www.scrum.org/resources/what-is-scrum)**: A short overview of what Scrum is
 -   **[Scrum Glossary](https://www.scrum.org/resources/scrum-glossary)**: A short Scrum glossary with the most essential terms
--   **[Scrum Values](https://kissflow.com/project/agile/how-to-apply-5-scrum-values/)**: Pracical examples of applying Scrum Values
+-   **[Scrum Values](https://kissflow.com/project/agile/how-to-apply-5-scrum-values/)**: Practical examples of applying Scrum Values
 
 ## More external resources
 

outdated/scrum/README.md

@@ -4,7 +4,7 @@
 -   Search for issues with the label `urgency:X` (where X is a number from 8 to 10) assigned to you (for developers, this would usually be critical bugs). You should include them into your next sprint - or do them right now if you have an empty backlog.
 -   After that, choose all unfinished "important"(1) issues from the previous sprint that you've not managed to finish. They should be carried over to the next sprint.
 -   Next pick "important"(1) issues selected by ProductOwner as goals for next sprint.
--   Finally, choose any other issues that will fill up your backlog so you have enough to do for the following sprint. Remember to pick these issues on what will get us most effectively/effeciently towards our short/mid/long-term goals and our vision.
+-   Finally, choose any other issues that will fill up your backlog so you have enough to do for the following sprint. Remember to pick these issues on what will get us most effectively/efficiently towards our short/mid/long-term goals and our vision.
 -   Don’t forget to include all critical issues and other urgent priority issues (if any) to the upcoming sprint.
 
 When you do the Sprint Planning, ahead of the Sprint Planning Meeting, then make sure to add `next sprint` label for all issues you are going to add to your backlog: it will help us to: