Iteration-4/Non-functional-requirements-verification.md

@@ -5,7 +5,7 @@ title: Non-functional requirements verification
 
 1. **_An emergency alert should be processed and visible in the ticket management page in less than 20 seconds after submitting it._**
 
-   **Result:** Backend logs show that alerts are inserted to database in **less than a second** and after refresing the ticket management page, the alert is visible there as well. Every time it takes only a few seconds. The manual work to refresh the page is also includes in this time, so in reality, this process takes maximum of few seconds. And as the processing time is so little, the amount of fields filled do not play a rolw - e.g. if all fields in the alert are filled or if some are left empty.
+   **Result:** Backend logs show that alerts are inserted to database in **less than a second** and after refresing the ticket management page, the alert is visible there as well. Every time it takes only a few seconds. The manual work to refresh the page is also includes in this time, so in reality, this process takes maximum of few seconds. And as the processing time is so little, the amount of fields filled do not play a role - e.g. if all fields in the alert are filled or if some unrequired are left empty.
 2. **_A picture should be uploaded to Google Drive in less than 1 minute after submitting an emergency alert._**
 
    **Result:** Backend logs show that a single picture will be uploaded to Google Drive every time in **less than 10 seconds**. Usually in a few seconds. And is accessible in the Drive itself too in a few seconds (title is the time of the alert submittion + number of the picture (e.g first or second picture of this alert)).