addressing review

tests/acceptance/features/apiSpaces/changeSpaces.feature

@@ -339,7 +339,7 @@ Feature: Change data of space
     When user "<user>" uploads a file inside space "Project Jupiter" owned by the user "Alice" with content "new content" to ".space/readme.md" using the WebDAV API
     Then the HTTP status code should be "<code>"
     And for user "<user>" the content of the file ".space/readme.md" of the space "Project Jupiter" should be "<expectedContent>"
-    When user "<user>" lists all available spaces via the GraphApi
+    When user "<user>" lists all available spaces via the Graph API
     And the JSON response should contain space called "Project Jupiter" owned by "Alice" with description file ".space/readme.md" and match
     """
     {

tests/acceptance/features/apiSpaces/listSpaces.feature

@@ -81,7 +81,7 @@ Feature: List and create spaces
     Given user "Brian" has been created with default attributes and without skeleton files
     And user "Brian" has created folder "folder"
     And user "Brian" has shared folder "folder" with user "Alice" with permissions "31"
-    When user "Alice" lists all available spaces via the GraphApi with query "$filter=driveType eq 'personal'"
+    When user "Alice" lists all available spaces via the Graph API with query "$filter=driveType eq 'personal'"
     Then the HTTP status code should be "200"
     And the JSON response should contain space called "Alice Hansen" and match
     """
@@ -434,7 +434,7 @@ Feature: List and create spaces
     And user "Brian" has uploaded file with content "this is a test file." to "test.txt"
     And the administrator has assigned the role "<userRole>" to user "Alice" using the Graph API
     And user "Brian" has shared file "/test.txt" with user "Alice"
-    When user "Alice" lists all available spaces via the GraphApi
+    When user "Alice" lists all available spaces via the Graph API
     Then the HTTP status code should be "200"
     And the JSON response should contain space called "Shares" owned by "Alice" and match
     """

tests/acceptance/features/apiSpaces/lockFiles.feature

@@ -91,7 +91,7 @@ Feature: lock files
   Scenario Outline: lock a file in the project space
     Given the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API
     And using spaces DAV path
-    And user "Alice" has created a space "Project" with the default quota using the GraphApi
+    And user "Alice" has created a space "Project" with the default quota using the Graph API
     And user "Alice" has uploaded a file inside space "Project" with content "some content" to "textfile.txt"
     And user "Alice" has shared a space "Project" with settings:
       | shareWith | Brian  |
@@ -117,7 +117,7 @@ Feature: lock files
   Scenario Outline: lock a file in the project space using file-id
     Given the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API
     And using spaces DAV path
-    And user "Alice" has created a space "Project" with the default quota using the GraphApi
+    And user "Alice" has created a space "Project" with the default quota using the Graph API
     And user "Alice" has uploaded a file inside space "Project" with content "some content" to "textfile.txt"
     And we save it into "FILEID"
     And user "Alice" has shared a space "Project" with settings:
@@ -144,7 +144,7 @@ Feature: lock files
   Scenario: viewer cannot lock a file in the project space
     Given the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API
     And using spaces DAV path
-    And user "Alice" has created a space "Project" with the default quota using the GraphApi
+    And user "Alice" has created a space "Project" with the default quota using the Graph API
     And user "Alice" has uploaded a file inside space "Project" with content "some content" to "textfile.txt"
     And we save it into "FILEID"
     And user "Alice" has shared a space "Project" with settings:
@@ -203,7 +203,7 @@ Feature: lock files
       | /remote.php/dav/spaces/<<FILEID>> |
       | /dav/spaces/<<FILEID>>            |
 
-    
+
    Scenario: viewer cannot lock a file in the shares using file-id
     Given user "Alice" has uploaded a file inside space "Alice Hansen" with content "some content" to "textfile.txt"
     And we save it into "FILEID"
@@ -214,4 +214,3 @@ Feature: lock files
     When user "Brian" locks file using file-id path "<dav-path>" using the WebDAV API setting the following properties
       | lockscope | exclusive   |
     Then the HTTP status code should be "403"
-

tests/acceptance/features/apiSpacesDavOperation/copyByFileId.feature

@@ -75,8 +75,6 @@ Feature: copying file using file id
 
 
   Scenario Outline: copy a file into a folder in project space
-    Given the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API
-    And user "Alice" has created a space "project-space" with the default quota using the Graph API
     Given the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API
     And user "Alice" has created a space "project-space" with the default quota using the Graph API
     And user "Alice" has created a folder "/folder" in space "project-space"
@@ -97,8 +95,6 @@ Feature: copying file using file id
   Scenario Outline: copy a file into a sub-folder in project space
     Given the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API
     And user "Alice" has created a space "project-space" with the default quota using the Graph API
-    And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API
-    And user "Alice" has created a space "project-space" with the default quota using the Graph API
     And user "Alice" has created a folder "folder/sub-folder" in space "project-space"
     And user "Alice" has uploaded a file inside space "project-space" with content "some data" to "textfile.txt"
     And we save it into "FILEID"