From 33430b7bff2ae66ea78b3444545e7d21e8ee2533 Mon Sep 17 00:00:00 2001 From: pfabri Date: Sun, 20 Nov 2016 18:19:43 +0100 Subject: [PATCH] Updated Memory model (markdown) --- Memory-model.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Memory-model.md b/Memory-model.md index 4fd8204..34303de 100644 --- a/Memory-model.md +++ b/Memory-model.md @@ -38,7 +38,7 @@ If you're in this situation, [JsonBuffer size calculator](https://bblanchon.gith In the second case, let's say you dynamically generate a JSON object tree of a random complexity so you can't put a limit based on that. But on the other hand, you don't want your program to crash because the object tree doesn't fit in memory. The solution here is to determine how much memory is available, or in other words how much memory you can afford for the JSON object tree. -### Why choosing fixed allocation? +### Why choose fixed allocation? This fixed allocation approach may seem a bit strange, especially if you are a desktop application developer used to dynamic allocation, but it makes a lot of sense in an embedded context: