doc: update final task description

angular/modules/demo/README-ENG.md

@@ -6,32 +6,32 @@ Task: one team representative need to give a short demo. The goal of the meeting
 
 ### Introduction
 
-- Introduce the team.  
-- Briefly explain what the project is and why it is needed.  
-- Show a simplified project architecture (e.g., we have an API from service X. We are building the frontend. The design was also created by us. We will demonstrate everything further).  
+- Introduce the team.
+- Briefly explain what the project is and why it is needed.
+- Show a simplified project architecture (e.g., we have an API from service X. We are building the frontend. The design was also created by us. We will demonstrate everything further).
 
 ### Demonstration
 
-- Show the idea and main features in a live application or on several slides.  
-- Present everything that is ready at the moment: frontend, backend, designs, completed tasks.  
+- Show the idea and main features in a live application or on several slides.
+- Present everything that is ready at the moment: frontend, backend, designs, completed tasks.
 
 ### Conclusion
 
-- One slide/list with the main difficulties that took the most time.  
-- Show the plan for further work and the tasks to be completed by the deadline.  
+- One slide/list with the main difficulties that took the most time.
+- Show the plan for further work and the tasks to be completed by the deadline.
 
 ## Differences from the Final Presentation
 
-Show what has been done so far. It doesn’t need to work perfectly or look polished. The goal is to report on completed tasks and describe the next steps.  
+Show what has been done so far. It doesn’t need to work perfectly or look polished. The goal is to report on completed tasks and describe the next steps.
 
-No need to go deep into details (NgRx, tests, libraries, technical decisions — they can be mentioned, but not explained in detail).  
+No need to go deep into details (NgRx, tests, libraries, technical decisions — they can be mentioned, but not explained in detail).
 
-Do not show the team’s workflow/process.  
+Do not show the team’s workflow/process.
 
-There will be no Q&A session.  
+There will be no Q&A session.
 
 ## Timing
 
-Total duration: 5–10 minutes.  
+Total duration: 5–10 minutes.
 
-Main focus — demonstrate what has been done so far.  
+Main focus — demonstrate what has been done so far.

react/modules/tasks/final.md

@@ -422,8 +422,8 @@ For the convenience of verification, it is **necessary** to record and post on Y
 
 - [ ] The Main page should contain general information about the developers, project, and course. - **10 points**
 - [ ] In the upper right corner there are 2 buttons: Sign In and Sign Up. - **10 points**
-- [ ] If the login token is valid and unexpired, the Sign In and Sign Up buttons are replaced with the "Main Page" button. - **10 points**
-- [ ] When the token expires - the user should be redirected to the Main page automatically. - **10 points**
+- [ ] If the user is authorized, there should be a Main Page button instead of Sign In and Sign Up buttons in the upper right corner. - **10 points**
+- [ ] If the token is expired/invalid - the user should be redirected from the private routes to the Main page (it might happen either automatically, on page refresh or on route change). - **10 points**
 - [ ] Pressing the Sign In / Sign up button redirects a user to the route with the Sign In / Sign up form. - **10 points**
 
 ### Sign In / Sign Up - max 50 points