From 59230babf3f66d0390e1e8246c1dee7437a3a0ad Mon Sep 17 00:00:00 2001 From: Paul Sokolovsky Date: Sun, 21 May 2017 17:31:12 +0300 Subject: [PATCH] Typo fix. --- ContributorGuidelines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ContributorGuidelines.md b/ContributorGuidelines.md index 59b476c..2ab036e 100644 --- a/ContributorGuidelines.md +++ b/ContributorGuidelines.md @@ -47,5 +47,5 @@ When you submit a pull request, please make sure that it's understood why you pr As an example of application of previous ideas, (semi-serious) "Django criteria" are introduced regarding adding new features, which are roughly superfluous, not overly important, or rather rare to use: * If you write your own code, and there's another way to achieve it with other existing features, please just do it this other way. -* If you port existing code, you'll likely find out that a lot of features missing, so adding all of them will be a lot of work, and will bloat MicroPython, and adding just one of few won't make a big difference. (So, just keep *porting*, by patching existing code to use facilities MicroPython already provides.) +* If you port existing code, you'll likely find out that a lot of features missing, so adding all of them will be a lot of work, and will bloat MicroPython, and adding just one or few won't make a big difference. (So, just keep *porting*, by patching existing code to use facilities MicroPython already provides.) * However, if you tried to run a big, well-known package, like Django, and found that only few features are missing to run it out of the box, without any patching, then we definitely would like to add them to be able claim that MicroPython can run Django ;-).