diff --git a/versioned_docs/version-4.5/apis/subsystems/question/index.md b/versioned_docs/version-4.5/apis/subsystems/question/index.md
index ca4d06539e..8dc379d899 100644
--- a/versioned_docs/version-4.5/apis/subsystems/question/index.md
+++ b/versioned_docs/version-4.5/apis/subsystems/question/index.md
@@ -31,7 +31,7 @@ So, when a particular question is attempted with a particular behaviour, the cor
 
 1. `question_engine` - this class is the main entry point into this part of the API.
 2. `question_attempt` - this represents a users attempt at on question. Since most of the time user's attempt a group of related questions together, and even more important class is `question_usage_by_activity`.
-3. `question state` - as stated above, question types and behaviours should have as much freedom as possible to present interesting educational interactions to users. But, on the other hand, parts of the system that use questions (e.g. the quiz) need to have some idea what is going on with each question. The various question states try to find an appropriate compromise, so the state of each question can be tracked, but without restricting the freedom of the question behaviours to work how they want.
+3. `question_state` - as stated above, question types and behaviours should have as much freedom as possible to present interesting educational interactions to users. But, on the other hand, parts of the system that use questions (e.g. the quiz) need to have some idea what is going on with each question. The various question states try to find an appropriate compromise, so the state of each question can be tracked, but without restricting the freedom of the question behaviours to work how they want.
 4. `question_display_options` - when questions are used, e.g. in a quiz, there may be limitations one what the user can see. For example, perhaps the student is only allowed to see the grade and feedback on their attempt after all students have finished. The display options class is how the quiz can control which bits should be visible when a question is rendered. In addition, depending on what state we are in with the question behaviour might also affect what is visible right now, so qbehaviour_plugins can modify the display options based on the current state of the question_attempt, as part of the rendering process.
 5. `core_question_renderer` - renders the overall layout of the questions. It works with the applicable qtype_ and qbehaviour_ renderer to render the details of the current attempt.