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 e2cfacef8eb407c00451ca0f806f633f5c5ad92c
Author: chaokunyang <[email protected]>
AuthorDate: Mon Sep 8 07:47:06 2025 +0000

    🔄 synced local 'docs/guide/' with remote 'docs/guide/'
---
 docs/guide/graalvm_guide.md            | 4 ++--
 docs/guide/java_serialization_guide.md | 2 +-
 docs/guide/row_format_guide.md         | 2 +-
 docs/guide/scala_guide.md              | 4 ++--
 4 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/docs/guide/graalvm_guide.md b/docs/guide/graalvm_guide.md
index 7de36c431..190614953 100644
--- a/docs/guide/graalvm_guide.md
+++ b/docs/guide/graalvm_guide.md
@@ -25,10 +25,10 @@ GraalVM `native image` can compile java code into native 
code ahead to build fas
 The native image doesn't have a JIT compiler to compile bytecode into machine 
code, and doesn't support
 reflection unless configure reflection file.
 
-Apache Foryâ„¢ runs on GraalVM native image pretty well. Fory generates all 
serializer code for `Fory JIT framework` and `MethodHandle/LambdaMetafactory` 
at graalvm build time. Then use those generated code for serialization at 
runtime without
+Apache Foryâ„¢ runs on GraalVM native image pretty well. Apache Foryâ„¢ generates 
all serializer code for `Fory JIT framework` and 
`MethodHandle/LambdaMetafactory` at graalvm build time. Then use those 
generated code for serialization at runtime without
 any extra cost, the performance is great.
 
-In order to use Fory on graalvm native image, you must create Fory as an 
**static** field of a class, and **register** all classes at
+In order to use Apache Foryâ„¢ on graalvm native image, you must create Fory as 
an **static** field of a class, and **register** all classes at
 the enclosing class initialize time. Then configure `native-image.properties` 
under
 `resources/META-INF/native-image/$xxx/native-image.properties` to tell graalvm 
to init the class at native image
 build time. For example, here we configure `org.apache.fory.graalvm.Example` 
class be init at build time:
diff --git a/docs/guide/java_serialization_guide.md 
b/docs/guide/java_serialization_guide.md
index 3889b5251..059668176 100644
--- a/docs/guide/java_serialization_guide.md
+++ b/docs/guide/java_serialization_guide.md
@@ -135,7 +135,7 @@ public class Example {
 
 ## Advanced Usage
 
-### Apache Foryâ„¢ creation
+### Fory creation
 
 Single thread fory:
 
diff --git a/docs/guide/row_format_guide.md b/docs/guide/row_format_guide.md
index 4b20f1600..099f03820 100644
--- a/docs/guide/row_format_guide.md
+++ b/docs/guide/row_format_guide.md
@@ -99,7 +99,7 @@ print(f"pickle end: {datetime.datetime.now()}")
 
 ### Apache Arrow Support
 
-Fory Format also supports automatic conversion from/to Arrow Table/RecordBatch.
+Apache Foryâ„¢ Row Format also supports automatic conversion from/to Arrow 
Table/RecordBatch.
 
 Java:
 
diff --git a/docs/guide/scala_guide.md b/docs/guide/scala_guide.md
index 81eb6b69f..fe3d0cdd9 100644
--- a/docs/guide/scala_guide.md
+++ b/docs/guide/scala_guide.md
@@ -19,7 +19,7 @@ license: |
   limitations under the License.
 ---
 
-Fory supports all scala object serialization:
+Apache Foryâ„¢ supports all scala object serialization:
 
 - `case` class serialization supported
 - `pojo/bean` class serialization supported
@@ -31,7 +31,7 @@ Scala 2 and 3 are both supported.
 
 ## Install
 
-To add a dependency on Apache Foryâ„¢scala for with sbt, use the following:
+To add a dependency on Apache Foryâ„¢ scala for with sbt, use the following:
 
 ```sbt
 libraryDependencies += "org.apache.fory" %% "fory-scala" % "0.12.2"


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to