commit a2fc89edaffafd9123c429269fef63b388df810c
parent c59b24dddbe63f19181e4bff97eeadf2afae40f9
Author: Vincent Forest <vincent.forest@meso-star.com>
Date: Mon, 9 Jan 2023 14:24:07 +0100
Fix a spelling mistake in the rnsp man page
Diffstat:
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/rnsp.5.scd b/doc/rnsp.5.scd
@@ -33,7 +33,7 @@ defined in a separate file, for example in an *smsh*(5) file. The number of
available properties and their order should match the geometric primitives
listed in the corresponding mesh.
-An *rnsp* file is actually a Star-Buffer file (see *sbuf*(5)). It starts with a
+A *rnsp* file is actually a Star-Buffer file (see *sbuf*(5)). It starts with a
header of 4 64-bit integers describing the layout of the data. The first integer
is a power of two (usually 4096) that defines the size of the memory page in
bytes to which the list of properties aligns (_pagesize_). The second integer
@@ -42,7 +42,7 @@ Finally, the 2 remaining integers store the memory size (8 bytes) and the
memory alignment (8 bytes) of the property set defined by geometric primitive.
Padding bytes follow the file header to align the listed properties to
-_pagesize_.
+_pagesize_.
For each geometric primitive, the properties are composed of a 32-bit integer,
which is the material identifier of the primitive (_matid_), and a 32-bit
