Latest comment: 4 months ago1 comment1 person in discussion
The topic development has been reviewed according to the marking criteria. Written feedback is provided below, plus see the general feedback page. Also check the page history for changes made whilst reviewing the plan. If you don't understand the feedback or would like further information, get in touch to discuss. Marks are available via UCLearn. Marks are based on the latest version before the due date.
Very brief description about self – consider expanding
Consider linking to your eportfolio page and/or any other professional online profile or resume such as LinkedIn. This is not required, but it can be useful to interlink your professional networks.
Latest comment: 2 months ago1 comment1 person in discussion
This chapter has been reviewed according to the marking criteria. Written feedback is provided below, plus there is a general feedback page. Please also check the chapter's page history to check for editing changes made whilst reviewing through the chapter. Chapter marks will be available via UCLearn along with social contribution marks and feedback. Keep an eye on Announcements.
Reasonably good—relevant theories are selected, described, and explained, with some room for improvement
Reduce general theoretical background (e.g., description of SDT). Instead, summarise and link to related resources (i.e., other book chapters and/or Wikipedia articles). Increase emphasis on substantive aspects of theory that relate directly to the specific topic (i.e., the sub-title question).
Builds reasonably well on Wikipedia articles but not related chapters by embedding interwiki links for key terms
Basic depth is provided about key theory(ies)
Basic use of tables, figures, and/or lists to clearly convey key theoretical information
Key citations are well used
Basic use of examples to illustrate theoretical concepts
Some sentences could be explained more clearly (e.g., see the [explain?] and [improve clarity] tags)
Some sentences are overly long. Strive for the simplest expression. Consider splitting longer sentences into two shorter sentences. Shorter words and sentences are more readable. Try conducting a readability analysis such as via https://www.webfx.com/tools/read-able/. This chapter gets a score of . Aim for 50+.
Avoid one sentence paragraphs. Communicate one idea per paragraph using three to five sentences.
Layout
The chapter is well structured, with major sections using sub-sections
Use the default heading style (e.g., remove additional numbers)
Remove abbreviations/citations from headings
Include an introductory paragraph before branching into the sub-sections (see [Provide more detail] tags)
Grammar
The grammar for some/many sentences could be improved (e.g., see [grammar?] tags); consider using a grammar checking tool, Studiosity, and/or peer feedback
Once an abbreviation has been established (e.g., RPG), use it consistently afterwards
Proofreading
More proofreading is needed (e.g., fix punctuation and typographical errors) to bring the quality of written expression closer to a professional standard
Good use of embedded in-text interwiki links to Wikipedia articles. Adding more interwiki links for the first mention of key words and technical concepts would make the text even more interactive. See example.
Add embedded in-text links to related book chapters. Embedding in-text links to related book chapters helps to integrate this chapter into the broader book project.
Reasonably good use of figure(s)
No use of table(s)
Basic use of feature box(es)
Reasonably good use of scenarios, case studies, or examples