[rtems-docs commit] eng: Fix typos

[Sebastian Huber]

Module:    rtems-docs
Branch:    master
Commit:    c881d1e7d80b0aacff7ef3f75af6c26d5236c366
Changeset: http://git.rtems.org/rtems-docs/commit/?id=c881d1e7d80b0aacff7ef3f75af6c26d5236c366

Author:    Matt Joyce <matthew.joyce at embedded-brains.de>
Date:      Mon Nov  7 11:20:20 2022 +0100

eng: Fix typos

---

 eng/prequalification.rst | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/eng/prequalification.rst b/eng/prequalification.rst
index ba1840a..0dddb15 100644
--- a/eng/prequalification.rst
+++ b/eng/prequalification.rst
@@ -15,7 +15,7 @@ standards typically do not specify software functionality but address
 topics like requirements definition, traceability, having a documented
 change process, coding style, testing requirements, and a user's
 manual. During system test, these standards call for a review - usually
-by an independent entity - that the standard has been adhered too. These
+by an independent entity - that the standard has been adhered to. These
 reviews cover a broad variety of topics and activities, but the process
 is generally referred to as qualification, verification, or auditing
 against the specific standard in use. The RTEMS Project will use the
@@ -83,8 +83,8 @@ Stakeholder Involvement
 
 Qualification of RTEMS is a specialized activity and only specific users
 of RTEMS will complete a formal qualification activity. The RTEMS Project
-cannot self-fund this entire activity and requires stakeholder to invest
-in an ongoing basis to ensure that any investment they make is maintained
-and viable in an ongoing basis. The RTEMS core developers view steady
+cannot self-fund this entire activity and requires stakeholders to invest
+on an ongoing basis to ensure that any investment they make is maintained
+and viable in the long-term. The RTEMS core developers view steady
 support of the qualification effort as necessary to continue to lower
 the overall costs of qualifying RTEMS.