From 6a3265022ac2dbc606e1d333b5356599d9efaaa9 Mon Sep 17 00:00:00 2001
From: Tianyi Pu <44583944+putianyi889@users.noreply.github.com>
Date: Mon, 25 Mar 2024 10:05:01 +0000
Subject: [PATCH] Update README.md

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index b3adbb9..0363d0b 100644
--- a/README.md
+++ b/README.md
@@ -45,5 +45,5 @@ where `some` can be `el`, `base` and `precision`.
 ### On `precisionconvert`
 `precisionconvert` accepts an optional third argument `prec`. 
 - When `T` has static precision, `prec` has no effect.
-- When `T` has dynamic precision, `prec` specifies the precision of conversion. When `prec` is not provided, the precision is decided by the external setup from `T`. The difference is significant when `precisionconvert` is called by another function:
+- When `T` has dynamic precision, `prec` specifies the precision of conversion. When `prec` is not provided, the precision is decided by the external setup from `T`. The difference is significant when `precisionconvert` is called by another function. See the document for an example.
 - When `T` is an integer, the conversion will dig into `Rational` as well. In contrast, since `Rational` as a whole is more "precise" than an integer, `precisiontype` doesn't unwrap `Rational`.