aboutsummaryrefslogtreecommitdiff
path: root/core/encoding
diff options
context:
space:
mode:
authorcui fliter <imcusg@gmail.com>2022-08-05 20:10:20 +0800
committercui fliter <imcusg@gmail.com>2022-08-05 20:10:20 +0800
commitdc8b7a0eb866d436cdaf4bb0c0dcd4c18962fa13 (patch)
treeb0f837441196b8c8ba6f138ebaf7d4572d7fd6bd /core/encoding
parent8d1f46d837efdcebaf2e3660942a93337a230329 (diff)
fix some typos
Signed-off-by: cui fliter <imcusg@gmail.com>
Diffstat (limited to 'core/encoding')
-rw-r--r--core/encoding/hxa/hxa.odin2
1 files changed, 1 insertions, 1 deletions
diff --git a/core/encoding/hxa/hxa.odin b/core/encoding/hxa/hxa.odin
index f47661bad..9b24ede9c 100644
--- a/core/encoding/hxa/hxa.odin
+++ b/core/encoding/hxa/hxa.odin
@@ -107,7 +107,7 @@ Node :: struct {
/* Conventions */
/* ------------
Much of HxA's use is based on convention. HxA lets users store arbitrary data in its structure that can be parsed but whose semantic meaning does not need to be understood.
-A few conventions are hard, and some are soft. Hard convention that a user HAS to follow in order to produce a valid file. Hard conventions simplify parsing becaus the parser can make some assumptions. Soft convenbtions are basicly recomendations of how to store common data.
+A few conventions are hard, and some are soft. Hard convention that a user HAS to follow in order to produce a valid file. Hard conventions simplify parsing becaus the parser can make some assumptions. Soft convenbtions are basically recomendations of how to store common data.
If you use HxA for something not covered by the conventions but need a convention for your use case. Please let us know so that we can add it!
*/