fix: typos in Vue Options API and Kotlin Defining Classes content (#9910)

- 'aproach' -> 'approach' and 'predicatably' -> 'predictably' in
  src/data/roadmaps/vue/content/options-api...md
- 'Defining Classess' -> 'Defining Classes' heading in
  src/data/roadmaps/kotlin/content/defining-classess...md
This commit is contained in:
ChrisJr404
2026-05-06 16:33:45 +02:00
committed by GitHub
parent 585189f715
commit 4e09326369
2 changed files with 2 additions and 2 deletions
@@ -1 +1 @@
# Defining Classess
# Defining Classes
@@ -1,6 +1,6 @@
# Options API
Vue offers many approaches for how to write components, including the Options API. It is the only API that is available in all versions of Vue. Its primary focus is on providing a consistent, clean, and organized aproach to writing component logic. Each part of a component's logic is given a dedicated section (data, methods, computed, props, life-cycle hooks, etc). By putting the logic in the correct section it has access to the features of the framework automatically. With the official Vue ESLint plugin the order of these sections can be enforced across all components allowing developers to predicatably locate any part of the component, even if they've never looked at the file before.
Vue offers many approaches for how to write components, including the Options API. It is the only API that is available in all versions of Vue. Its primary focus is on providing a consistent, clean, and organized approach to writing component logic. Each part of a component's logic is given a dedicated section (data, methods, computed, props, life-cycle hooks, etc). By putting the logic in the correct section it has access to the features of the framework automatically. With the official Vue ESLint plugin the order of these sections can be enforced across all components allowing developers to predictably locate any part of the component, even if they've never looked at the file before.
Visit the following resources to learn more: