diff --git a/solara/website/pages/api/use_state_or_update.py b/solara/website/pages/api/use_state_or_update.py
index 4671ae8ff..342084585 100644
--- a/solara/website/pages/api/use_state_or_update.py
+++ b/solara/website/pages/api/use_state_or_update.py
@@ -14,7 +14,7 @@
 
 @solara.component
 def SliderWithoutState(value: int):
-    # Note that this is very bad practive, if value is an input change and the slider
+    # Note that this is a very bad practice, if value is an input change and the slider
     # can change it, this component should have a on_value callback to allow the parent
     # component to manage its state.
     # This component is only for demoing/understanding.
diff --git a/solara/website/pages/docs/content/20-understanding/10-reacton.md b/solara/website/pages/docs/content/20-understanding/10-reacton.md
index 19bd6f786..18c830a93 100644
--- a/solara/website/pages/docs/content/20-understanding/10-reacton.md
+++ b/solara/website/pages/docs/content/20-understanding/10-reacton.md
@@ -16,7 +16,7 @@ We consider Solara a superset of Reacton, and that's why the full namespace of t
 Therefore, you can write `solara.use_state` or `reacton.use_state`, they are the same function.
 
 The reason for this is simplicity for newcomers, who don't care about the difference between `solara` and `reacton`.
-But in practive, it also saves having to import both `solara` and `reacton`.
+But in practice, it also saves having to import both `solara` and `reacton`.
 Also, when writing Solara based apps, one does not think about Reacton anymore, it is all Solara.
 
 ## How do I use Reacton or Solara with ipywidget library X