This is an automated email from the ASF dual-hosted git repository.

chaokunyang pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/fory-site.git

commit 5e78f7871f2a994a2fef4657c47c7c24074a44cc
Author: chaokunyang <shawn.ck.y...@gmail.com>
AuthorDate: Fri Jul 18 06:33:07 2025 +0000

    🔄 synced local 'docs/specification/' with remote 'docs/specification/'
---
 docs/specification/java_serialization_spec.md  | 2 +-
 docs/specification/xlang_serialization_spec.md | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/specification/java_serialization_spec.md 
b/docs/specification/java_serialization_spec.md
index 3a8d4bbe..2aa12b5f 100644
--- a/docs/specification/java_serialization_spec.md
+++ b/docs/specification/java_serialization_spec.md
@@ -393,7 +393,7 @@ which will be encoded by elements header, each use one bit:
 - If the collection has null, use the second bit `0b10` of the header to flag 
it. If ref tracking is enabled for this
   element type, this flag is invalid.
 - If the collection element types are not declared type, use the 3rd bit 
`0b100` of the header to flag it.
-- If the collection element types are different, use the 4rd bit `0b1000` 
header to flag it.
+- If the collection element types are different, use the 4th bit `0b1000` 
header to flag it.
 
 By default, all bits are unset, which means all elements won't track ref, all 
elements are same type, not null and
 the actual element is the declared type in the custom class field.
diff --git a/docs/specification/xlang_serialization_spec.md 
b/docs/specification/xlang_serialization_spec.md
index 58ac5778..66ced931 100644
--- a/docs/specification/xlang_serialization_spec.md
+++ b/docs/specification/xlang_serialization_spec.md
@@ -615,7 +615,7 @@ which will be encoded by elements header, each use one bit:
 - If the elements have null, use the second bit `0b10` of the header to flag 
it. If ref tracking is enabled for this
   element type, this flag is invalid.
 - If the element types are not the declared type, use the 3rd bit `0b100` of 
the header to flag it.
-- If the element types are different, use the 4rd bit `0b1000` header to flag 
it.
+- If the element types are different, use the 4th bit `0b1000` header to flag 
it.
 
 By default, all bits are unset, which means all elements won't track ref, all 
elements are same type, not null and
 the actual element is the declared type in the custom type field.


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@fory.apache.org
For additional commands, e-mail: commits-h...@fory.apache.org

Reply via email to