From 2bfe678f4d357811ba7c3fe079630611b51948ea Mon Sep 17 00:00:00 2001
From: dajiaohuang <108231307+dajiaohuang@users.noreply.github.com>
Date: Sun, 18 Oct 2026 20:07:37 +0800
Subject: [PATCH] docs: fix data-model custom tag example and formatter name

Add the missing colon to the custom-tag example and correct the formatter method to Model.to_pretty_xml().
---
 docs/topics/data-models.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/topics/data-models.mdx b/docs/topics/data-models.mdx
index ada59cdd..9b268b32 100644
--- a/docs/topics/data-models.mdx
+++ b/docs/topics/data-models.mdx
@@ -66,7 +66,7 @@ Notice that the name of our interior field (`.fact`) isn't relevant to the XML s
 If you want to separate the model tag from it's class name, you specify it in the class construction:
 
 ```python
-class FunFact(rg.Model, tag="a-super-fun-fact")
+class FunFact(rg.Model, tag="a-super-fun-fact"):
     ...
 ```
 
@@ -181,7 +181,7 @@ class Person(rg.Model):
 
 For primitive models, using the default `.xml_tags()` or `.xml_example()` works well for communicating to the model how it should respond, however for more complex models it's **highly recommended** to overload the `.xml_example()` method to provide a more detailed example of the XML structure you expect.
 
-The easiest way to approach this overload is to instantiate your model class with a few standard values and use `.to_prety_xml()`.
+The easiest way to approach this overload is to instantiate your model class with a few standard values and use `.to_pretty_xml()`.
 
 ```python
 import rigging as rg