From 8827d41747cde6362df294e0e3d65fa0f81c7924 Mon Sep 17 00:00:00 2001 From: Sela Date: Tue, 19 Feb 2019 14:09:45 +0000 Subject: [PATCH] Update index.md --- Resources/doc/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Resources/doc/index.md b/Resources/doc/index.md index bc3858fc..50b79298 100644 --- a/Resources/doc/index.md +++ b/Resources/doc/index.md @@ -169,7 +169,7 @@ This is absolutely no problem, just follow the instructions given in the corresp > Why didn't you implement the _delete_ feature provided by Fine Uploader? -FineUploaders _delete Feature_ is using generated unique names we would have to store in order to track down which file to delete. But both the storage and the deletetion of files are tight-coupled with the logic of your very own implementation. This means we leave the _delete Feature_ open for you to implement. Information on how the route must be crafted can be found on the [official documentation](http://docs.fineuploader.com/features/delete.html) and on [the blog](http://blog.fineuploader.com/2013/01/delete-uploaded-file-in-33.html) of Fine Uploader. +FineUploaders _delete Feature_ is using generated unique names we would have to store in order to track down which file to delete. But both the storage and the deletetion of files are tight-coupled with the logic of your very own implementation. This means we leave the _delete Feature_ open for you to implement. Information on how the route must be crafted can be found on the [official documentation](http://docs.fineuploader.com/features/delete.html) and on [the blog](https://blog.fineuploader.com/delete-an-uploaded-file-in-3-3-3623bf6ec9c) of Fine Uploader. > Why didn't you implement the _delete_ feature provided by another library?