Updated Differences (markdown)

Differences.md

@@ -26,7 +26,7 @@ Some features don't cater for constrained systems, and at the same time are not
 1. `async with` should be equivalent to [PEP492 description](https://www.python.org/dev/peps/pep-0492/#asynchronous-context-managers-and-async-with).
 1. `async for` should be equivalent to [PEP492 description](https://www.python.org/dev/peps/pep-0492/#asynchronous-iterators-and-async-for).
 1. There's no support for "Future-like objects" with `__await__` method. `await` can be used only on coroutines and generators (not "Future-like objects"). It's also just a syntactic sugar for "yield from" and thus accepts iterables and iterators, which are not allowed in CPython.
-1. Instance `__dict__` is read-only, so `foo.__dict__['bar'] = 23` or `foo.__dict__.update({'bar': 23)` does not work. [#1757](//github.com/micropython/micropython/issues/1757) [#2139](//github.com/micropython/micropython/issues/2139)
+1. Instance `__dict__` is read-only, so `foo.__dict__['bar'] = 23` or `foo.__dict__.update({'bar': 23})` does not work. [#1757](//github.com/micropython/micropython/issues/1757) [#2139](//github.com/micropython/micropython/issues/2139)
 
 ## Known Issues
 Known issues are essentially bugs, misfeatures, and omissions considered such, and scheduled to be fixed. So, ideally any entry here should be accompanied by bug ticket reference. But note that these known issues will have different priorities, especially within wider development process. So if you are actually affected by some issue, please add details of your case to the ticket (or open it if does not yet exist) to help planning. Submitting patches is even more productive. (Please note that the list of not implemented modules/classes include only those which are considered very important to implement; per the above, MicroPython does not provide full standard library in general.)