addressed reviews

Author: KarunAtreya

tests/acceptance/features/apiWebdavLocks/publicLink.feature

@@ -94,7 +94,7 @@ Feature: persistent-locking in case of a public link
       | old                       | shared     |
       | old                       | exclusive  |
 
-  @skipOnOcV10
+    @skipOnOcV10
     Examples:
       | public-webdav-api-version | lock-scope |
       | new                       | shared     |

tests/acceptance/features/apiWebdavLocks/publicLinkOc10Issue40882.feature

@@ -1,16 +1,14 @@
-@api @smokeTest @public_link_share-feature-required @files_sharing-app-required @issue-40882
+@api @smokeTest @public_link_share-feature-required @files_sharing-app-required
 Feature: persistent-locking in case of a public link
 
-  Background:
+
+  Scenario Outline: Public locking is not supported
     Given user "Alice" has been created with default attributes and without skeleton files
     And user "Alice" has created folder "PARENT"
     And user "Alice" has created folder "PARENT/CHILD"
     And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "PARENT/parent.txt"
     And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "PARENT/CHILD/child.txt"
-
- 
-  Scenario Outline: Public locking is not supported
-    Given user "Alice" has created a public link share of folder "PARENT" with change permission
+    And user "Alice" has created a public link share of folder "PARENT" with change permission
     When the public locks "/CHILD" in the last public link shared folder using the <public-webdav-api-version> public WebDAV API setting the following properties
       | lockscope | <lock-scope> |
     Then the HTTP status code should be "403"