From 0af5d0fcbc25a07b7ecf2abbddd9644930f8ee52 Mon Sep 17 00:00:00 2001
From: ringabout <43030857+ringabout@users.noreply.github.com>
Date: Thu, 5 Feb 2026 20:15:21 +0800
Subject: [PATCH] fix

---
 doc/manual.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/manual.md b/doc/manual.md
index 75dc4ead57..18c9a0099b 100644
--- a/doc/manual.md
+++ b/doc/manual.md
@@ -1144,7 +1144,7 @@ semantic analysis). Assignments from the base type to one of its subrange types
 A subrange type has the same size as its base type (`int` in the
 Subrange example).
 
-Implicit "downsizing" conversions to range types (for example, `int -> range[0..255]` or `range[1..256] -> range[0..255]`) emit the `ImplicitRangeConversion` warning. Conversions that are clearly safe (for example, `range[0..255] -> range[0..65535]`) and any explicit casts do not trigger this warning. Conversions from `int` to common subranges such as `Natural` or `Positive` are also exempt, which can be enabled with `--warning:systemRangeConversion`
+Implicit "downsizing" conversions to range types (for example, `int -> range[0..255]` or `range[1..256] -> range[0..255]`) emit the `ImplicitRangeConversion` warning. Conversions that are clearly safe (for example, `range[0..255] -> range[0..65535]`) and any explicit casts do not trigger this warning. Conversions from `int` to common subranges such as `Natural` or `Positive` are also exempt, which can be enabled with `--warning:systemRangeConversion`.
 
 
 Pre-defined floating-point types