[Buildroot] [PATCH 6/6] website/lts: fix typos

[Thomas Perale via buildroot <buildroot@buildroot.org>]

Signed-off-by: Thomas Perale <thomas.perale@mind.be>
---
 docs/website/lts.html | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/docs/website/lts.html b/docs/website/lts.html
index fd684ab3a9..3bfd2a4374 100644
--- a/docs/website/lts.html
+++ b/docs/website/lts.html
@@ -29,7 +29,7 @@
                 3-year LTS support
             </h2>
             <p class="br-lts-item-text">
-            Starting with version <code>2025.02</code> the LTS support has been extended to
+            Starting with version <code>2025.02</code>, the LTS support has been extended to
             <strong>3 years</strong>, replacing the previous 1-year cycle.
             </p>
         </div>
@@ -65,7 +65,7 @@
             <p class="br-lts-item-text">
             To ensure a consistent release cadence and maintenance
             workflow, paid LTS stewards are assigned to the weekly LTS
-            maintainance tasks.
+            maintenance tasks.
             </p>
         </div>
     </div>
@@ -96,7 +96,7 @@
     The Buildroot LTS sponsorship initiative has evolved from a more
     comprehensive understanding of the needs of our user base.
     <br/>
-    To address these requirements the release model evolves into the following.
+    To address these requirements, the release model evolves into the following.
     <br/>
     The LTS releases are now extended for a 3-year period. An LTS release
     is started every 2 years.
@@ -177,12 +177,12 @@
     </div>
 
     <p>
-    Each week the LTS stewards defines the set of commits to
-    analyze based on the previous week commits to the master branch. The
+    Each week, the LTS stewards define the set of commits to
+    analyze based on the previous week's commits to the master branch. The
     commits are then annotated to define a list of candidates for the LTS
     branches.
     <br><br>
-    On Thursday the candidates are cherry-picked to a staging branch to be
+    On Thursday, the candidates are cherry-picked to a staging branch to be
     reviewed by the other maintainers. On Thursday evening the branch is
     synced with upstream and contributors are notified. Feedback from
     users, sponsors and autobuilders are then collected and vulnerability
-- 
2.53.0

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot