From 88da904e9e2dc2c35d5608916242a60b8bdcbe3c Mon Sep 17 00:00:00 2001 From: Andrea Giammarchi Date: Wed, 9 Oct 2024 17:08:45 +0200 Subject: [PATCH] Fix typo (#36285) --- .../javascript/reference/global_objects/json/rawjson/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/files/en-us/web/javascript/reference/global_objects/json/rawjson/index.md b/files/en-us/web/javascript/reference/global_objects/json/rawjson/index.md index a5608c09f4de86a..745d6ee12900453 100644 --- a/files/en-us/web/javascript/reference/global_objects/json/rawjson/index.md +++ b/files/en-us/web/javascript/reference/global_objects/json/rawjson/index.md @@ -45,7 +45,7 @@ JSON.stringify({ value: 12345678901234567890 }); The value is not exactly equivalent to the original number any more! This is because JavaScript uses floating point representation for all numbers, so it cannot represent all integers exactly. The number literal `12345678901234567890` itself is already rounded to the nearest representable number when it is parsed by JavaScript. -Without `JSON.rawJSON`, there is no way to tell `JSON.stringify` to produce the number literal `12345678901234567000`, because there is simply no corresponding JavaScript number value. With raw JSON, you can directly tell `JSON.stringify()` what a particular value should be stringified as: +Without `JSON.rawJSON`, there is no way to tell `JSON.stringify` to produce the number literal `12345678901234567890`, because there is simply no corresponding JavaScript number value. With raw JSON, you can directly tell `JSON.stringify()` what a particular value should be stringified as: ```js const rawJSON = JSON.rawJSON("12345678901234567890");