fmt

Author: reteps

src/pages/about/blog/self-enrollment-overhaul/index.mdx

@@ -36,27 +36,26 @@ Let's get into all the new features!
 
 There are now additional features for managing enrollments in your course instance.
 
-<BlogImage 
-  src={selfEnrollmentSettingsFull} 
+<BlogImage
+  src={selfEnrollmentSettingsFull}
   alt="Overview of self-enrollment settings"
   caption="The full self-enrollment settings panel with all available options"
   full
 />
 
-
 #### Explicit invitations and disabling self-enrollment
 
 If you want to no longer allow students to self-enroll, you can disable self-enrollment.
 
 You can then manage access by explicitly inviting students to your course. These invitations will show up on the homepage for students to accept an invitation.
 
-<BlogImage 
-  src={inviteStudent} 
+<BlogImage
+  src={inviteStudent}
   alt="Invitation modal"
   caption="Inviting students to a course instance"
 />
-<BlogImage 
-  src={acceptInvitationHomepage} 
+<BlogImage
+  src={acceptInvitationHomepage}
   alt="Invitation on homepage"
   caption="Students can see and accept invitations directly from their homepage"
 />
@@ -80,7 +79,8 @@ Students will then be able to join via the homepage or the special self-enrollme
 If the code gets leaked, you can regenerate the enrollment code. This will invalidate the old enrollment code.
 
 <BlogCalloutBox variant="info">
-  We recommend most instructors enable this option, and distribute the self-enrollment code in their course materials.
+  We recommend most instructors enable this option, and distribute the
+  self-enrollment code in their course materials.
 </BlogCalloutBox>
 
 #### Institution self-enrollment limits
@@ -115,8 +115,8 @@ via the 'Students' or 'Gradebook' tab.
 From this page, you can now manage their enrollment status. At any point, you can block a student, which will immediately
 deny them access to the course instance.
 
-<BlogImage 
-  src={blockedStudent} 
+<BlogImage
+  src={blockedStudent}
   alt="Blocked student"
   caption="A blocked student is immediately denied access to the course instance. They can later be unblocked"
 />
@@ -128,8 +128,8 @@ Publishing is a rework of the course instance access control system.
 
 #### Unpublished course instances
 
-<BlogImage 
-  src={unpublished} 
+<BlogImage
+  src={unpublished}
   alt="Unpublished course"
   caption="Unpublished course instances are only visible to staff, not students"
 />
@@ -146,8 +146,8 @@ When a course instance is published, students will be able to enroll in it and a
 When preparing for a new term, you can setup your course instance to be published in the future. On that date,
 the course instance will switch to published.
 
-<BlogImage 
-  src={scheduledPublish} 
+<BlogImage
+  src={scheduledPublish}
   alt="Scheduled publishing"
   caption="You can schedule a course instance to be published automatically on a future date"
 />
@@ -163,13 +163,13 @@ The most common usecase for customized access rules for a course instance was to
 You can now manage these extensions directly through the UI. These extensions are not written to the JSON config, as we move away from
 PII/user emails in JSON configuration files.
 
-<BlogImage 
-  src={addExtension} 
+<BlogImage
+  src={addExtension}
   alt="Add extension"
   caption="You can grant extensions to specific students directly through the UI"
 />
-<BlogImage 
-  src={publishedWithExtensions} 
+<BlogImage
+  src={publishedWithExtensions}
   alt="Published with extensions"
   caption="A published course instance with extensions showing which students have extended access"
 />
@@ -211,4 +211,6 @@ Please let us know in [Slack](/slack) or on [GitHub](https://github.com/PrairieL
 
 export default ({ children }) => (
   <BlogMarkdownLayout meta={meta}>{children}</BlogMarkdownLayout>
-);
+);
+
+;