diff options
| author | Spencer McIntyre <zeroSteiner@gmail.com> | 2016-08-26 07:00:16 -0400 |
|---|---|---|
| committer | Spencer McIntyre <zeroSteiner@gmail.com> | 2016-08-26 07:00:16 -0400 |
| commit | 244e2cbc74c06d73fea288cb94c684de2332e7f1 (patch) | |
| tree | 1843e24018e67ccd814a1ff12a95257c3c18a4b7 | |
| parent | 3ad92592a45a6482ceb65dead13cb0eb13193ae4 (diff) | |
| parent | 3c812c10e78e779dabbfb686590886652b1548b0 (diff) | |
| download | pluginbase-244e2cbc74c06d73fea288cb94c684de2332e7f1.tar.gz | |
Land #12, fix a typo in index.rst
| -rw-r--r-- | docs/index.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/index.rst b/docs/index.rst index b2de86b..6c34e09 100644 --- a/docs/index.rst +++ b/docs/index.rst @@ -76,7 +76,7 @@ Q: Why is there a plugin base and a plugin source class? Q: Do plugins pollute ``sys.modules``? While a plugin source is alive the plugins do indeed reside in - ``sys.modules``. This decision was make conciously so that as little + ``sys.modules``. This decision was made consciously so that as little as possible of the Python library ecosystem breaks. However when the plugin source gets garbage collected all loaded plugins will also get garbage collected. |