diff options
| author | Gabor Greif <ggreif@gmail.com> | 2017-01-23 09:38:15 +0100 |
|---|---|---|
| committer | Gabor Greif <ggreif@gmail.com> | 2017-01-23 11:27:22 +0100 |
| commit | 80560e69ca40abb2c94c4e9fa322365f558a6a8b (patch) | |
| tree | ba0122a93709a34daeb4db992651e98f3937dc7e /docs/users_guide/safe_haskell.rst | |
| parent | 2b64e926a628fb2a3710b0360123ea73331166fe (diff) | |
| download | haskell-80560e69ca40abb2c94c4e9fa322365f558a6a8b.tar.gz | |
Typos and grammar in manual/comments
Diffstat (limited to 'docs/users_guide/safe_haskell.rst')
| -rw-r--r-- | docs/users_guide/safe_haskell.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/users_guide/safe_haskell.rst b/docs/users_guide/safe_haskell.rst index 653b741339..13797ac534 100644 --- a/docs/users_guide/safe_haskell.rst +++ b/docs/users_guide/safe_haskell.rst @@ -85,7 +85,7 @@ due to the presence of functions like ``unsafePerformIO``. Safe Haskell gives users enough guarantees about the type system to allow them to build such secure systems. -As an example, lets define an interface for a plugin system where the +As an example, let's define an interface for a plugin system where the plugin authors are untrusted, possibly malicious third-parties. We do this by restricting the plugin interface to pure functions or to a restricted ``IO`` monad that we have defined. The restricted ``IO`` @@ -137,7 +137,7 @@ We then compile the ``Danger`` plugin using the new Safe Haskell runMe :: RIO () runMe = ... -Before going into the Safe Haskell details, lets point out some of the +Before going into the Safe Haskell details, let's point out some of the reasons this security mechanism would fail without Safe Haskell: - The design attempts to restrict the operations that ``Danger`` can perform by |