From 6c85ec1a6d9b072f2afb1a8669d1ffa963cc6b05 Mon Sep 17 00:00:00 2001 From: Jakub Wilk Date: Tue, 5 Sep 2017 00:16:56 +0200 Subject: [PATCH] Fix typos. --- docs/docs/development.rst | 2 +- docs/docs/features.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/docs/development.rst b/docs/docs/development.rst index 36a6e539..90027ecd 100644 --- a/docs/docs/development.rst +++ b/docs/docs/development.rst @@ -14,7 +14,7 @@ Introduction ------------ This page tries to address the fundamental demand for documentation of the -|jedi| interals. Understanding a dynamic language is a complex task. Especially +|jedi| internals. Understanding a dynamic language is a complex task. Especially because type inference in Python can be a very recursive task. Therefore |jedi| couldn't get rid of complexity. I know that **simple is better than complex**, but unfortunately it sometimes requires complex solutions to understand complex diff --git a/docs/docs/features.rst b/docs/docs/features.rst index fd5b3bab..03361c77 100644 --- a/docs/docs/features.rst +++ b/docs/docs/features.rst @@ -109,7 +109,7 @@ option than to execute those modules. However: Execute isn't that critical (as e.g. in pythoncomplete, which used to execute *every* import!), because it means one import and no more. So basically the only dangerous thing is using the import itself. If your ``c_builtin`` uses some strange initializations, it -might be dangerous. But if it does you're screwed anyways, because eventualy +might be dangerous. But if it does you're screwed anyways, because eventually you're going to execute your code, which executes the import.