docs: polish

Author: brillout

docs/pages/event-based/+Page.mdx

@@ -24,7 +24,7 @@ You may be tempted to create generic telefunctions but we recommend against it.
 ```ts
 // database/todo.telefunc.ts
 
-// ❌ Generic telefunction: one telefunction re-used for multiple use case
+// ❌ Generic telefunction: one telefunction re-used for multiple use cases
 export async function updateTask(id: number, modifications: Partial<TodoItem>) {
   // ...
 }
@@ -34,6 +34,7 @@ export async function updateTask(id: number, modifications: Partial<TodoItem>) {
 // components/TodoList.telefunc.ts
 
 // ✅ Event-based telefunctions: one telefunction per use case
+
 export async function onTodoTextUpdate(id: number, text: string) {
   // ...
 }
@@ -43,7 +44,7 @@ export async function onTodoCompleted(id: number) {
 ```
 
 In the example below, we explain why event-based telefunctions lead to increased:
- - Development speed (and we explain how to keep things DRY)
+ - Development speed (while we explain how to keep telefunctions DRY)
  - Security
  - Performance
 
@@ -129,7 +130,7 @@ This naming convention ensures telefunctions are tightly coupled to UI component
 
 #### Too restrictive convention?
 
-To keep things [DRY](https://softwareengineering.stackexchange.com/questions/400183/what-should-i-consider-when-the-dry-and-kiss-principles-are-incompatible) you may be tempted to define a single telefunction that is re-used by many UI components. For example:
+To keep telefunctions [DRY](https://softwareengineering.stackexchange.com/questions/400183/what-should-i-consider-when-the-dry-and-kiss-principles-are-incompatible) you may be tempted to define a single telefunction that is re-used by many UI components. For example:
 
 ```ts
 // database/actions/tasks.telefunc.ts
@@ -214,8 +215,7 @@ That's why we recommend event-based telefunctions, along with the naming convent
 
 ## Naming convention
 
-As explained in <Link href="#example">the example above</Link>, for a clear structure and more effective use of Telefunc, we recommend the following convention.
-
+As explained in <Link href="#example">the example above</Link>, for a clear structure and efficient Telefunc usage, we recommend the following convention.
 
 Name telefunctions `onSomeEvent()`:
 
@@ -257,5 +257,5 @@ Telefunc shows a warning if you don't follow the naming convention — you can o
 
 ## See also
 
-- <Link href="/multiple-clients" />
 - <Link href="/disableNamingConvention" />
+- <Link href="/multiple-clients" />