I am making use case specification for Edutopia. I have the following actors and their use cases:
User: Read Article, Search Article, Comment includes Login
educator: Submit Article includes Login
editor: Review Article, Update Article, Publish Article
admin: Manage users, Manage website

I have made the following use case specification:
###
2.2	Functional Requirements Specification

This section delineates the use cases for each of the actors involved in the Edutopia system. The actors include Users, Educators, Editors, and Admins, each with specific roles and functionalities within the system.
2.2 Functional Requirements Specification
This section outlines the use cases for each active user type within Edutopia.
2.2.1 User Use Cases
•	Use Case: Search Article
o	Brief Description: A user can search for articles within the Edutopia system by author, category, or keyword.
o	Initial Step-by-Step Description: 
1.	The user accesses the Edutopia website.
2.	The user chooses a search type: author, category, or keyword.
3.	The system presents relevant options based on the search type selected.
4.	The user selects their desired search criteria.
5.	The system displays a list of articles matching the criteria.
6.	The user selects a specific article.
7.	The system displays the article's abstract.
o	Xref: Section 3.2.1, Search Article
•	Use Case: Read Article
o	Brief Description: A user can read the full text of a selected article.
o	Initial Step-by-Step Description 
1.	The User accesses the article detail view (following a search or direct link).
2.	The system displays the complete article content.
o	Xref: Section 3.2.2, Read Article
•	Use Case: Comment
o	Brief Description: A logged-in user can leave comments on an article.
o	Initial Step-by-Step Description: 
1.	The user accesses an article's detail view.
2.	The user navigates to the comments section.
3.	The user enters their comment in the provided text field.
4.	The user submits their comment.
5.	The system processes the comment, applying any necessary moderation or filtering.
6.	The system displays the user's comment along with other existing comments.
o	Xref: Section 3.2.3, Comment
2.2.2 Educator Use Cases
•	Use Case: Submit Article 
o	Brief Description: An educator can submit an article for consideration in Edutopia.
o	Initial Step-by-Step Description: 
1.	The educator accesses a designated article submission area.
2.	The educator fills out a submission form including title, abstract, article content (as a file attachment), and relevant metadata.
3.	The educator submits the form.
4.	The system acknowledges receipt and assigns a tracking identifier.
o	Xref: Section 3.2.4, Submit Article
2.2.3 Editor Use Cases
•	Use Case: Review Article
o	Brief Description: An editor reviews a submitted article.
o	Initial Step-by-Step Description: 
1.	The editor accesses a list of pending articles.
2.	The editor selects an article to review.
3.	The system displays the full article content and metadata.
4.	The editor assesses the article based on relevance, quality, and alignment with Edutopia's guidelines.
5.	The editor records their assessment (e.g., accept, reject, revisions required) and provides feedback to the educator.
o	Xref: Section 3.2.5, Review Article
•	Use Case: Update Article
o	Brief Description: An editor modifies details of an article (before or after publication)
o	Initial Step-By-Step Description: 
1.	The editor accesses a list of articles.
2.	The editor selects the article to be updated.
3.	The system presents an editable form with the article details.
4.	The editor modifies fields as needed (title, authors, content, categories, status, etc.).
5.	The editor saves the changes.
o	Xref: Section 3.2.6, Update Article
•	Use Case: Publish Article
o	Brief Description: An editor marks an accepted article as published, making it available on Edutopia.
o	Initial Step-By-Step Description: 
1.	The editor accesses a list of accepted articles.
2.	The editor selects an article to publish.
3.	The system changes the article's status to "Published."
4.	The system updates the Edutopia website to display the published article.
o	Xref: Section 3.2.7, Publish Article
2.2.4 Admin Use Cases
Use Case: Manage Users Brief Description The Admin manages the user accounts and permissions on the Edutopia website.
Initial Step-By-Step Description Before this use case can be initiated, the Admin has logged in to the Edutopia admin dashboard.
1.	The Admin selects the "Manage Users" option.
2.	The system displays a list of all registered Edutopia users.
3.	The Admin can view user details, assign roles and permissions, activate/deactivate accounts, and perform other user management tasks.
4.	The Admin submits the changes, and the system updates the user database accordingly.
Xref: Section 3.2.8, Manage Users
Use Case: Manage Website Brief Description The Admin manages the content, structure, and settings of the Edutopia website.
Initial Step-By-Step Description Before this use case can be initiated, the Admin has logged in to the Edutopia admin dashboard.
1.	The Admin selects the "Manage Website" option.
2.	The system presents the website management interface.
3.	The Admin can update page content, modify the navigation structure, configure website settings, and perform other website management tasks.
4.	The Admin submits the changes, and the system updates the website accordingly.
Xref: Section 3.2.9, Manage Website
###

Now, based on this format, write detailed functional requirement for each usecase as mentioned in Xref and use format in table for each use case:
example format:
3.2.1	Update Article Status
Use Case Name:	Update Article Status
XRef:	Section 2.2.4, Update Article
Trigger: The Editor selects to update the status of an article in the database.
Precondition: The Editor has accessed the Article Manager main screen and the article is already in the database.
Basic Path:
1.	The system creates and presents an alphabetical list of all active articles.
2.	The Editor selects the article to update.
3.	The system presents the information about the article in grid format.
4.	The Editor updates the information and resubmits the form.
Alternative Paths:
In step 4, the use case Enter Communication may be invoked.
Postcondition: The database has been updated.
Exception Paths:
If the article is not already in the database, the use case is abandoned. In addition, the Editor may abandon the operation at any time.
Other:
This use case can be used to add categories for an article, to correct typographical errors, or to remove a reviewer who has missed a deadline for returning a review. It may also be used to allow access to the named use case to enter an updated article or a review for an article.