Skip to content

Commit c76d28c

Browse files
authored
Update synced-file-moved-to-recycle-bin.md
1 parent 5bdeb1d commit c76d28c

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

SharePoint/SharePointOnline/sync/synced-file-moved-to-recycle-bin.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -25,14 +25,14 @@ When you synchronize a Microsoft SharePoint Online library or a OneDrive library
2525

2626
## Cause
2727

28-
This issue occurs because a user accidentally deleted the file, or the file was removed by a local application for a user who was synchronizing the library.
28+
This issue occurs because a user accidentally deleted the file, or a local application for the user who synchronized the library deleted the file.
2929

3030
## More information
3131

3232
If a folder is deleted from a locally synced SharePoint library, the OneDrive sync client processes this action as a standard file system deletion. The OneDrive sync client then syncs this change to the cloud (SharePoint/OneDrive). When other users who synced the same library receive this update, their devices also delete the folder locally. Therefore, the operating system moves the deleted folder into each user’s local recycle bin. The OneDrive client makes sure that local folders and the cloud library are kept in sync. This process also applies to empty folders.
3333

34-
To determine who might have deleted the affected file, check the **Deleted By** field for affected file in the SharePoint Online or OneDrive recycle bin. The account that's listed in this field is for the user who performed the delete operation.
34+
To determine who might have deleted the affected file, open the SharePoint Online or OneDrive recycle bin, and then check the **Deleted By** field for affected file. The account that's listed in this field is for the user who performed the delete operation.
3535

36-
You can verify that the file wasn't intentionally or accidentally deleted by the identified user. This is important if multiple users are synchronizing a single library. For example, in some cases, a user might try to copy a file that might have been accidentally moved to another directory. This action removes the file from the synchronized library.
36+
You can determine whether the file was intentionally or accidentally deleted by the identified user. This information is important if multiple users are synchronizing a single library. For example, in some cases, a user might try to copy a file that might have been accidentally moved to another directory. This action removes the file from the synchronized library.
3737

38-
If the file wasn't intentionally or accidentally deleted by the user who's listed in the **Deleted By** field, ask the user to determine whether a local process moved or deleted the file. For example, local virus-protection software might be configured to quarantine files.
38+
If the file wasn't intentionally or accidentally deleted by the **Deleted By** user, ask the user to determine whether a local process might have moved or deleted the file. For example, local virus-protection software could be configured to quarantine files.

0 commit comments

Comments
 (0)