Fix typos in course examination section (#26)

Author: zezl7

docs/course-information.md

@@ -38,7 +38,7 @@ We encourage **you** to help us extend these resources and fix mistakes.
 
 ## Exam
 
-The course has a so-called *"course accompanying examination"*. This means, there will be no single exam. Instead, we evaluate the students' performance on the individual challenge, on the weekly exercises, and on the overall engagement. Still, wou will have to register for the *"exam"* on campus. **Point of no return**: Once you gave the first presentation (presumably early November), you have to register.
+The course has a so-called *"course accompanying examination"*. This means, there will be no single exam. Instead, we evaluate the students' performance on the individual challenge, on the weekly exercises, and on the overall engagement. Still, you will have to register for the *"exam"* on campus. **Point of no return**: Once you gave the first presentation (presumably early November), you have to register.
 
 ## Additional information for SimTech students
 
@@ -48,4 +48,4 @@ You might also be interested in the course *Sustainable Development of Simulatio
 
 > This paragraph is meant for developers maintaining repositories to which students of the SSE course try to contribute.
 
-One of the learning goals of the SSE course is being able to contribute to existing large-scale research codes. One part of the course is to indeed contribute something small to such a code. As a maintainer of such a code, please treat the students as normal (experienced) external contributors. They learn in the SSE course how to follow contribution guidelines and other best practices. As a maintainer, you do not have to advise them as closely as you might do with your own students. Following your own contribution standards and code of conduct is sufficient. You can help the students by labeling suitable existing isues as *good first issues*. We, the [lecturers of the SSE course](staff.md), try to follow conversations of our students in issues or pull requests as closely as possible. You can always tag us on GitHub or directly reach out to us. Each year, we are giving the students a list of software projects as suggestions on where to contribute. If you ever want us to remove your project from this list, please let us know.
+One of the learning goals of the SSE course is being able to contribute to existing large-scale research codes. One part of the course is to indeed contribute something small to such a code. As a maintainer of such a code, please treat the students as normal (experienced) external contributors. They learn in the SSE course how to follow contribution guidelines and other best practices. As a maintainer, you do not have to advise them as closely as you might do with your own students. Following your own contribution standards and code of conduct is sufficient. You can help the students by labeling suitable existing issues as *good first issues*. We, the [lecturers of the SSE course](staff.md), try to follow conversations of our students in issues or pull requests as closely as possible. You can always tag us on GitHub or directly reach out to us. Each year, we are giving the students a list of software projects as suggestions on where to contribute. If you ever want us to remove your project from this list, please let us know.