Skip to content

Commit 60fb7dd

Browse files
committed
docs: correct typos
closes: #17 Signed-off-by: Philipp Ahmann <[email protected]>
1 parent b93ff19 commit 60fb7dd

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

docs/get_involved.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ The :underline:`only` way to influence S-CORE is TO CONTRIBUTE. Everybody can co
4242

4343
Active Contributions to the S-CORE project are the basis for getting involved. The S-CORE Project works according to
4444
the Eclipse Project Handbook and has named and elected project leads and committers (see https://projects.eclipse.org/projects/automotive.score/who).
45-
Direction of the S-CORE project is discussed and decided in the project lead circle, technical direction is created and prediscussed in the tech
45+
Direction of the S-CORE project is discussed and decided in the project lead circle, technical direction is created and discussed upfront in the tech
4646
lead circle. Meeting notes are transparent via the S-CORE github organization. (see https://github.com/orgs/eclipse-score/discussions)
4747

4848
We aim to build a safety ready full stack architecture, where components fit to each other in

docs/index.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -151,7 +151,7 @@ Here you can find the preliminary roadmap of the project:
151151
:align: center
152152

153153

154-
Please be aware, that this roadmap will be also transfered to the `GitHub project <https://github.com/orgs/eclipse-score/projects/13>`_.
154+
Please be aware, that this roadmap will be also transferred to the `GitHub project <https://github.com/orgs/eclipse-score/projects/13>`_.
155155
Please follow this link to get the latest state of the planning.
156156

157157
MVP Phase
@@ -162,8 +162,8 @@ The main goals of the *MVP Phase* are following:
162162
* establish a working infrastructure, that enables every developer of the project to specify
163163
requirements and architecture, implement code and test it accordingly.
164164
* set-up project structure, that covers all aspects of the open source software development including
165-
cooperation between developers and teams, planning, creation of the roadmaps and coordination meetings.
166-
* define a software development process compliant to ISO 26262:2018, that is a prerequiste for any other software development in the project.
165+
cooperation between developers and teams, planning, creation of the roadmap and coordination meetings.
166+
* define a software development process compliant to ISO 26262:2018, that is a prerequisite for any other software development in the project.
167167

168168
A lot of preparation was already done in the background, therefore we are quite optimistic to finish the *MVP Phase*
169169
latest in the beginning of 2025.
@@ -185,7 +185,7 @@ the interest of the automotive community to the project.
185185
Series Stability & Evolution Phase
186186
==================================
187187

188-
In this phase the project should be in an well established state and accepted by the community. Continious development
188+
In this phase the project should be in an well established state and accepted by the community. Continuous development
189189
of the features is taking place.
190190

191191
How we Work

0 commit comments

Comments
 (0)