#7 - fix misspellings

features/admin_panel/access_to_admin_panel.feature

@@ -11,4 +11,4 @@ Feature: Access to admin panel
   Scenario: Unauthorized access
     Given I am not logged in as an admin user
     When I get to admin panel route
-    Then I should see "You do not have access"
+    Then I should see "You do not have access"

features/admin_panel/adding_user_to_admin_panel.feature

@@ -17,11 +17,11 @@ Feature:
     | email                     |
     | firstuser@example.com     |
 
-  Scenario Outline: Invited user already are admin
+  Scenario Outline: Invited user is already an administrator
     Given user with <email> already are admin user
     When I fill "email" with <email>
     And I send the form
-    Then I should see message "This user already are admin user"
+    Then I should see message "This user is already an administrator"
     Examples:
       | email                         |
-      | existingadmin@example.com     |
+      | existingadmin@example.com     |

features/admin_panel/creating_new_admin.feature

@@ -9,21 +9,22 @@ Feature: Creating new admin user
       | user@example.com         |
 
   Scenario: Invited user already have account
-    Given I get to authentication route by invitation link
-    When I log in as "[email protected]"
+    Given Invited user get to authentication route by invitation link
+    When I log in as <email>
     Then I become admin user
 
   Scenario Outline: Successfully created an account
     Given I get to authentication route by invitation link
     When I fill "email" with <email>
-    And I fill "password" with <password>>
+    And I fill "password" with <password>
     And I fill "name" with <name>
     Then I create new account with email <email>
     And I become admin user
     Examples:
       | email                    | password       | name       |
       | user@example.com         | validpassword  | newadmin   |
-  Scenario: Invitation is expired
-    Given Invitation was send more than 7 days ago
+
+  Scenario: Invitation has expired
+    Given invitation was send more than 7 days ago
     When I get to authentication route by invitation link
-    Then I should see message "Your invitation is expired"
+    Then I should see message "Your invitation is expired"

features/admin_panel/meetup_crud.feature

@@ -15,7 +15,7 @@ Feature: Meetup CRUD operations
     And I fill the "date" with <date>
     And I fill the "place" with <place>
     And I fill the "language" with <language>
-    Then New meetup with matching data should be created
+    Then new meetup with matching data should be created
     And I should see message "Meetup was created"
     Examples:
       | title                    | date                 | place           | language |
@@ -31,4 +31,4 @@ Feature: Meetup CRUD operations
     And I should see message "Meetup was updated"
     Examples:
       | id | title                 | date                 | place              | language |
-      | 1  | updated meetup        | 2024-02-02 10:10:10  | updated place      | en       |
+      | 1  | updated meetup        | 2024-02-02 10:10:10  | updated place      | en       |

features/admin_panel/organization_crud.feature

@@ -13,7 +13,7 @@ Feature: Organization CRUD operations
     Given I am on the create organization page
     When I fill the "name" with <name>
     And I fill the "description" with <description>
-    Then New organization with matching data should be created
+    Then new organization with matching data should be created
     And I should see message "Organization was created"
     Examples:
       | name                     | description          |
@@ -27,4 +27,4 @@ Feature: Organization CRUD operations
     And I should see message "Organization was updated"
     Examples:
       | id | name                    | description          |
-      | 1  | updated organization    | updated organization  |
+      | 1  | updated organization    | updated organization  |

features/admin_panel/speakers_crud.feature

@@ -13,7 +13,7 @@ Feature: Speaker CRUD operations
     Given I am on the create speaker page
     When I fill the "name" with <name>
     And I fill the "description" with <description>
-    Then New speaker with matching data should be created
+    Then new speaker with matching data should be created
     And I should see message "Speaker was created"
     Examples:
       | name                | description          |
@@ -27,4 +27,4 @@ Feature: Speaker CRUD operations
     And I should see message "Speaker was updated"
     Examples:
       | id | name                    | description          |
-      | 1  | updated speaker         | updated speaker      |
+      | 1  | updated speaker         | updated speaker      |

features/authentication/login.feature

@@ -5,26 +5,26 @@ Feature: Logging to app
       | email                    | password        |
       | existinguser@example.com | correctpassword |
 
-  Scenario Outline: attempt to log in with correct credentials
+  Scenario Outline: Attempt to log in with correct credentials
     When I fill "email" with <email>
-    And I fill "password" with <password>
-    Then I have successfully logged in
+    And I "password" with <password>
+    Then I successfully logged in
     Examples:
       | email                    | password        |
       | existinguser@example.com | correctpassword |
 
-  Scenario Outline: attempt to log in with wrong password
+  Scenario Outline: Attempt to log in with wrong password
     When I fill "email" with <email>
     And I fill "password" with <password>
     Then I should see message "bad credentials"
     Examples:
       | email                       | password           |
       | existinguser@example.com    | wrongpassword      |
 
-  Scenario Outline: attempt to log in as unregistered user
+  Scenario Outline: Attempt to log in as unregistered user
     When I fill "email" with <email>
     And I fill "password" with <password>
     Then I should see message "bad credentials"
     Examples:
       | email                       | password           |
-      | nonexistinguser@example.com | password           |
+      | nonexistinguser@example.com | password           |

features/authentication/register.feature

@@ -1,19 +1,24 @@
 Feature: Register to app
 
+  Background:
+    Given I am on the register page
+
   Scenario Outline: Register with valid data
-    When I fill "email" with <email>
-    And I fill "password" with <password>
-    And I fill "name" with <name>
+    When I fill "email" with "<email>"
+    And I fill "password" with "<password>"
+    And I fill "name" with "<name>"
+    And I submit form
     Then I have successfully sign up
     And I should get an email on <email>
     Examples:
       | email                    | password        | name          |
       | existinguser@example.com | correctpassword | existinguser  |
 
   Scenario: Register using existing email
-    Given there are following users
+    Given there are following users:
       | email                    | password        |
       | existinguser@example.com | password        |
     When I fill "email" with "[email protected]"
     And I fill "password" with "password"
-    Then I should see message "User with this email actually exist"
+    And I submit form
+    Then I should see message "User with this email actually exist"

features/meetup/meetup_crud.feature

@@ -18,7 +18,7 @@ Feature: Meetup CRUD operations
     And I fill the "place" with <place>
     And I fill the "language" with <language>
     And I submit form
-    Then New meetup with matching data should be created
+    Then new meetup with matching data should be created
     And Organizer id should be 1
     And I should see message "Meetup was created"
     Examples: