From d2adef97e14eb3421a44738c231bbf1392b26e90 Mon Sep 17 00:00:00 2001 From: pfalcon Date: Thu, 11 Dec 2014 14:44:36 -0800 Subject: [PATCH] Typos. --- ContributorGuidelines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ContributorGuidelines.md b/ContributorGuidelines.md index b79b1a3..29de102 100644 --- a/ContributorGuidelines.md +++ b/ContributorGuidelines.md @@ -1,6 +1,6 @@ # What to contribute -MicroPython is named "Micro" for a reason. We don't want to compete with CPython or replace it. We could spend year of development and do everything what CPython can do, just in 50% of size. It's not worthy an aim. If you want all CPython functionality, you can use CPython right now. What we try to achieve with MicroPython is being order(s) of magnitude smaller than CPython, to use Python (the language) where CPython could not be used at all. This necessitates being a CPython subset, making compromises for what can go into MicroPython core, and then stay orthodox about these compromises. +MicroPython is named "Micro" for a reason. We don't want to compete with CPython or replace it. We could spend years of development and implement everything what CPython can do, just in 50% of size. It's not worthy an aim. If you want all CPython functionality, you can use CPython right now. What we try to achieve with MicroPython is being order(s) of magnitude smaller than CPython, to use Python (the language) where CPython could not be used at all. This necessitates being a CPython subset, making compromises for what can go into MicroPython core, and then stay orthodox about these compromises. Here are more specific examples: