diff options
| author | CyberDrudge <satyamsaxena197@gmail.com> | 2019-01-18 19:40:49 +0530 |
|---|---|---|
| committer | CyberDrudge <satyamsaxena197@gmail.com> | 2019-01-18 19:40:49 +0530 |
| commit | f0baf1d4e41f5fc34383c3700b69de82a6d2982f (patch) | |
| tree | f76fe5eb3b34684b87cbf5f75cc39067bef4e631 | |
| parent | 173c275b4f4758d7c3c0cfae11ae48aa708de39d (diff) | |
| -rw-r--r-- | docs/intro/data-availability.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/intro/data-availability.rst b/docs/intro/data-availability.rst index cf65428e..9154d383 100644 --- a/docs/intro/data-availability.rst +++ b/docs/intro/data-availability.rst @@ -10,7 +10,7 @@ or his application data from the cloud. In many ways, data availability has become a necessary precondition for an application to be considered "user friendly". Unfortunately, most applications attempt to provide high data availability by rolling their own custom solution -or relying on a third party API, such as Dropbox. This approach is has several +or relying on a third party API, such as Dropbox. This approach has several drawbacks: the user has no control or access to the data should they wish to switch applications or data providers; custom data synchronizations schemes are often an afterthought, poorly designed, and vulnerable to attack and data |