feat(spec): standardizing fury cross-language serialization specification

docs/guide/xlang_type_mapping.md

@@ -0,0 +1,7 @@
+---
+title: Type Mapping of Xlang Serialization
+sidebar_position: 3
+id: xlang_type_mapping
+---
+
+Coming soon.

docs/protocols/README.md

@@ -1,4 +1,4 @@
 # Serialization Protocols
+- For Cross Language Object Graph Protocol, see [xlang_object_graph_format_spec](./xlang_object_graph_spec.md) doc.
 - For Java Object Graph Protocol, see [java_object_graph_format_spec](java_object_graph_spec.md) doc.
-- For Cross Language Object Graph Protocol, see [xlang_object_graph_format_spec](./xlang_object_graph.md) doc.
 - For Row Format Protocol, see [row format_spec](./row_format.md) doc.

docs/protocols/java_object_graph_spec.md

@@ -172,7 +172,7 @@ Meta header is a 64 bits number value encoded in little endian order.
  meta
  for such types is written separately instead of inlining here is to reduce meta space cost if object of this
  type is serialized in current object graph multiple times, and the field value may be null too.
- - List Type Info: list type will have an extra byte for elements info.
+ - Collection Type Info: collection type will have an extra byte for elements info.
  Users can use annotation to provide those info.
  - elements type same
  - elements tracking ref
@@ -211,7 +211,7 @@ Same encoding algorithm as the previous layer except:
 
 ## Meta String
 
-Meta string is mainly used to encode meta strings such class name and field names.
+Meta string is mainly used to encode meta strings such as class name and field names.
 
 ### Encoding Algorithms