[gtk/matthiasc/for-master] fixup! node-editor: Document the node format

[Matthias Clasen <matthiasc src gnome org>]

commit 325c5ce8888ec903ac5daedb5d9f28a2d716b7ff
Author: Matthias Clasen <mclasen redhat com>
Date:   Mon Jun 29 00:00:46 2020 -0400

    fixup! node-editor: Document the node format
    
    Fix a typo

 demos/node-editor/node-format.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
---
diff --git a/demos/node-editor/node-format.md b/demos/node-editor/node-format.md
index 083bf1f828..42bb90fe72 100644
--- a/demos/node-editor/node-format.md
+++ b/demos/node-editor/node-format.md
@@ -1,6 +1,6 @@
 # The Node file format
 
-GSK render nodes can be serialized and deserialized using APIs such as `gsk_render_node_serialize()` and 
`gsk_render_node_desrialize()`. The intended use for this is development - primarily the development of GTK - 
by allowing things such as creating testsuites and benchmarks, exchanging nodes in bug reports. GTK includes 
the `gtk4-node-editor` application for creating such test files.
+GSK render nodes can be serialized and deserialized using APIs such as `gsk_render_node_serialize()` and 
`gsk_render_node_deserialize()`. The intended use for this is development - primarily the development of GTK 
- by allowing things such as creating testsuites and benchmarks, exchanging nodes in bug reports. GTK 
includes the `gtk4-node-editor` application for creating such test files.
 
 The format is a text format that follows the [CSS syntax rules](https://drafts.csswg.org/css-syntax-3/). In 
particular, this means that every array of bytes will produce a render node when parsed, as there is a 
defined error recovery method. For more details on error handling, please refer to the documentation of the 
aprsing APIs.