Typos and Grammar

000 Inbox/00 ❗ Readme.md

@@ -24,7 +24,7 @@ This note serves to explain the fundamental theory of LDP.
 ### Who is this for?
 LDP is a life-management framework for those who find themselves distracted by the modern world. LDP will create meaning (Life), direction (Disciplines), and action (Projects). If you are missing either of these, you may find LDP useful.
 
-Fully utilizing LDP requires a moderate amount of setup (mainly self-reflection). You can post-pone this step if needed If need something working now.
+Fully utilizing LDP requires a moderate amount of setup (mainly self-reflection). You can post-pone this step if you need something working now.
 
 ### What can you get from this?
 - [[Philosophy - How to Approach LDP|How you should approach LDP]]

600 Resources/Disciplines.md

@@ -3,12 +3,12 @@ aliases: Discipline
 tags: [ info, productivity ]
 ---
 # Disciplines
-A **Discipline** is a pathway of [[Life (LDP)|Life]]. Disciplines have a set of [[Pillars]] that when combined forms a [[Dynamics|Dynamic]].
+A **Discipline** is a pathway of [[Life (LDP)|Life]]. Disciplines have a set of [[Pillars]] that when combined form a [[Dynamics|Dynamic]].
 
 Some disciplines may be considered as [[Ikigai]].
 
 ## Scoping
-Disciplines should be distinguishable from each other. You should not have **Mental Health** and **Well-Being** since the two are tightly woven together. One exception is if you specialize in Mental Health for school, then it may be better to separate the two.
+Disciplines should be distinguishable from each other. You should not have **Mental Health** and **Well-Being** since the two are tightly woven together. One possible exception might be if you specialize in Mental Health for school, then it may be better to separate the two.
 
 ## Relations and Placement
 Disciplines are immediately related to your [[Ikigai|Life]], as Disciplines are the components of one's lifestyle.

600 Resources/Dynamics.md

@@ -5,6 +5,6 @@ tags: [ info ]
 # Dynamics
 **Dynamics** is the multiplicative experience that comes as a result of combining components to make a system.
 
-An example of this is a living room. At it's core componenets, it's merely a room, a couch, television, lighting, and a coffee table. But when combined together, it becomes a shared space and common ground for the family and guests to safely interact with, along many other emerging Dynamics.
+An example of this is a living room. At it's core components, it's merely a room, a couch, television, lighting, and a coffee table. But when combined together, it becomes a shared space and common ground for the family and guests to safely interact with, along many other emerging Dynamics.
 
 For the a better understanding of higher-ordered Dynamics, see [[Systems Thinking]].

600 Resources/Fundamentals of LDP.md

@@ -37,9 +37,9 @@ The exact methods of how you align are up to you, but the main point is to force
 
 ### Core Components
 #### Resources
-[[Resources]] are your general useful notes and media that you can reference later. This is particularly useful if you wish to curate new ideas from existing ones, or if you want need reference material as reminders.
+[[Resources]] are your general useful notes and media that you can reference later. This is particularly useful if you wish to curate new ideas from existing ones, or if you need reference material as reminders.
 
-> This is not the place for extremely specific resources related to an LDP core component. A note specfically for an Programming project may only be useful for that project and no where else. This note should be archived under 📁`900 Archive`.
+> This is not the place for extremely specific resources related to an LDP core component. A note specfically for a Programming project may only be useful for that project and no where else. This note should be archived under 📁`900 Archive`.
 
 #### Tasks
 [[Tasks]] are items of action. To lessen friction, they should have an estimated work time less than 2 hours.
@@ -80,8 +80,8 @@ Habits can be thought of as repeating [[#Tasks]].
 #### Projects
 [[Projects]] are derived from Disciplines. 
 
-If Disciplines defined the direction, Projects generate the speed, resulting in velocity.
+If Disciplines define the direction, Projects generate the speed, resulting in velocity.
 
-Projects have a single objective, which should uphold or to make progress towards a Discipline's Pillars or Dynamics. Similar to Tasks, they should also have some sort of Completion Criteria to denote when this project is clearly completed.
+Projects have a single objective, which should uphold or make progress towards a Discipline's Pillars or Dynamics. Similar to Tasks, they should also have some sort of Completion Criteria to denote when this project is clearly completed.
 
-Projects should take no longer than an estimated month of work and no shorter than 2 hours to complete. *This is merely a suggestion to reduce friction.*
+Projects should take no more than an estimated month of work and no less than 2 hours to complete. *This is merely a suggestion to reduce friction.*

600 Resources/Habits.md

@@ -5,7 +5,7 @@ tags: [info]
 # Habits
 **Habits** are regular practices or routines that are small and easy, and are part of a bigger system of personal compound growth.
 
-Habits stick once they are performed subconsciously, but this may take anywhere between 18-254 days. The key is consistency and exposure through a system that includes, but not limited to:
+Habits stick once they are performed subconsciously, but this may take anywhere between 18-254 days. The key is consistency and exposure through a system that includes, but is not limited to:
 - Active and Passive Reminders
 - Progress Tracking
 - [[Fundamentals of LDP#Alignment]]

600 Resources/Inbox.md

@@ -3,4 +3,4 @@ aliases:
 tags: [info, productivity]
 ---
 # Inbox
-Your inbox is where temporay work goes into. It may not fit into any [[Disciplines|Discipline]] or [[Projects|Project]] a this moment, or you may not want to deal with sorting it at the moment.
+Your inbox is where temporary work goes into. It may not fit into any [[Disciplines|Discipline]] or [[Projects|Project]] at this moment, or you may not want to deal with sorting it at the moment.

600 Resources/Projects.md

@@ -3,7 +3,7 @@ aliases: Project
 tags: [ info, productivity ]
 ---
 # Projects
-**Projects** are derived from [[Disciplines]] and has some Objective that requires some set of [[Tasks]] to complete. These Projects should make progress towards or uphold some [[Pillars|Pillar]] from the parent discipline.
+**Projects** are derived from [[Disciplines]] and have some Objective that requires some set of [[Tasks]] to complete. These Projects should make progress towards or uphold some [[Pillars|Pillar]] from the parent discipline.
 
 Projects should strongly fit into one Discipline, and if it seems a Project could fit in multiple, the Disciplines need to be reorganized to prevent overlapping dependency, where too many items from one discipline belong in another Discipline. Just combine the two or figure out some other way to have them clearly different.
 
@@ -15,7 +15,7 @@ While there isn't a real maximum on how big a Project is, it's suggested to be n
 ## Relations and Placement
 Projects should be placed within a dedicated projects folder.
 
-Tasks are largely derived from Projects to make lee-way towards meeting the Objective, which in term, meets the discipline's pillars and/or [[Dynamics|Dynamic]].
+Tasks are largely derived from Projects to make leeway towards meeting the Objective, which in term, meets the discipline's pillars and/or [[Dynamics|Dynamic]].
 
 ## Abstract
 Explains the context of the project. Generally discusses the following.
@@ -31,7 +31,7 @@ All Objectives should minimally answer the following questions.
 ## Completion Criteria
 Unlike [[Disciplines]], Projects should eventually come to an end and shouldn't run any longer than 1 month. Since there usually isn't a time-based ending point ([[True Deadlines|True Deadline]]), an end must be defined through some other means.
 
-For Projects, a Completion Criteria is a well-defined checklist that cumulate to a shift in the environment or creation of a deliverable. 
+For Projects, a Completion Criteria is a well-defined checklist that culminates in a shift in the environment or the creation of a deliverable. 
 
 Well-Defined as in, requirements can be clearly answered `Yes` or `No` if they have been met. These Requirements should align with the Core.
 

600 Resources/Tasks.md

@@ -5,28 +5,28 @@ tags: [ info, productivity ]
 # Tasks
 **Tasks** are Actionable items with a clearly defined completion. You should be able to read this Task and trivially answer `Yes` or `No` as to if this Task is complete. 
 
-Tasks should work towards some Objective denoted in the corresponding [[Projects|Project]]; or uphold or works towards some [[Disciplines|Discipline]].
+Tasks should work towards some Objective denoted in the corresponding [[Projects|Project]]; or uphold or work towards some [[Disciplines|Discipline]].
 
-Tasks are Pull-based, meaning pull a task into your *Working On* list as you have more free hands, up to the [[#Ongoing]] limit. This concept of Pulling is similar to [[Kanban (Agile)|Kanban]]'s task management.
+Tasks are Pull-based, meaning you pull a task into your *Working On* list as you have more hands free, up to the [[#Ongoing]] limit. This concept of Pulling is similar to [[Kanban (Agile)|Kanban]]'s task management.
 
 ### Planned
-Tasks tagged with `#planned` are tasks in your queue. They are to be worked on sometime today, or soon. 
+Tasks tagged with `#planned` are tasks in your queue. They are to be worked on sometime today, or soon.
 
 Try to have at max 5 planned tasks at any given time.
 
-Consder checking out [[Planned Tasks]].
+Consider checking out [[Planned Tasks]].
 
 ### Ongoing
-Sets this task is currently being worked on should have the `#ongoing` tag on it.
+When a task is currently being worked on it should have the `#ongoing` tag on it.
 
-All `#ongoing` Tasks will be aggregated by Obsidian Tasks.
+All `#ongoing` Tasks will be aggregated by [Obsidian Tasks](https://github.com/schemar/obsidian-tasks).
 
 There should be no more than 3 `#ongoing` tasks at any time. This is to reduce friction.
 
 See [[Ongoing Tasks]] on what constitutes as an `#ongoing` task.
 
 ## Relation
-Tasks are largely related to [[Projects]] as Tasks make lee-way towards its Objectives.
+Tasks are largely related to [[Projects]] as Tasks make leeway towards their Objectives.
 
 Tasks may also be a part of Disciplines and Life as needed.
 
@@ -41,7 +41,7 @@ To allow for aggregation of tasks through the [Obsidian Tasks](https://github.co
 `< >` - required
 `[ ]` - optional
 
-Due dates are to be handled by the [[Due]] template and [Natural Language Dates in Obsidian](https://github.com/argenos/nldates-obsidian.
+Due dates are to be handled by the [[Due]] template and [Natural Language Dates in Obsidian](https://github.com/argenos/nldates-obsidian).
 
 > **Feel free to not use Obsidian Tasks. Do what works for you.**