docs(content): Fix doc wording

It seemed like "change" was referenced too many times in the same sentence.
Kitware · May 26, 2022 · 490196e · 490196e
1 parent 4c2ba6d
commit 490196e
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/docs/content/docs/trame_v2_intro.md b/docs/content/docs/trame_v2_intro.md
@@ -1,6 +1,6 @@
 # Trame v2
 
-First of all, Trame v2 is not changing the ideas and concepts that made trame what it is. This new version is really focusing on a more powerful and refined suite for creating Python application effortlessly while supporting many deployment type. With trame we aim to support desktop, client/server, cloud services and Jupyter notebook without changing a single line of code change.
+First of all, Trame v2 is not changing the ideas and concepts that made trame what it is. This new version is really focusing on a more powerful and refined suite for creating Python application effortlessly while supporting many deployment type. With trame we aim to support desktop, client/server, cloud services and Jupyter notebook without changing a single line of code.
 
 ![trame](/trame/images/trame-architecture.jpg)
 
@@ -18,4 +18,4 @@ With trame v2, we are deprecating PyWebVue in favor of our trame suite (trame +
 
 Also now that we have formalized how new Python modules should interface with trame. The community can more simply extend trame with their new widgets and/or UI elements.
 
-Now you might be wondering if a trame v3 is planed with yet another breaking change in another 6 months? Well to be honest we may have released too early pywebvue and trame but they were so game changer that it was hard to keep them for ourself. To be honest, I don't see a v3 anytime soon as v2 has gave us a chance to review our api, fixed what we didn't like and provide an easy path across our various use-cases.
+Now you might be wondering if a trame v3 is planed with yet another breaking change in another 6 months? Well to be honest we may have released too early pywebvue and trame but they were so game changer that it was hard to keep them for ourself. To be honest, I don't see a v3 anytime soon as v2 has gave us a chance to review our api, fixed what we didn't like and provide an easy path across our various use-cases.