diff --git a/Golang-ppc64x-asm-Reference.md b/Golang-ppc64x-asm-Reference.md
index 9f50573..68a04c6 100644
--- a/Golang-ppc64x-asm-Reference.md
+++ b/Golang-ppc64x-asm-Reference.md
@@ -153,8 +153,8 @@ In Go assembly, the naming conventions for function definitions are as follows:
 
 我感觉AI回答的不是十分正确，·funcname(SB)是最常用到的，感觉更应该是package level function。
 
-In Go assembly, the · symbol is used to denote a global symbol. When you define a global symbol like ·mask, it's expected to be unique in the entire program. If you try to define ·mask more than once, you'll get a duplicate symbol definition error.
+In Go assembly, the `·` symbol is used to denote a global symbol. When you define a global symbol like `·mask`, it's expected to be unique in the entire program. If you try to define `·mask` more than once, you'll get a duplicate symbol definition error.
 
-On the other hand, mask<> is a local symbol. Local symbols are only visible within the file they are defined in. You can have a mask<> symbol in each assembly file in your program, and they won't conflict with each other because they are not visible outside their own files.
+On the other hand, `mask<>` is a local symbol. Local symbols are only visible within the file they are defined in. You can have a `mask<>` symbol in each assembly file in your program, and they won't conflict with each other because they are not visible outside their own files.
 
-So, the difference comes from the scope of the symbols. Global symbols like ·mask are visible throughout the entire program and must be unique. Local symbols like mask<> are only visible within their own file and can be defined in each file without causing conflicts.
+So, the difference comes from the scope of the symbols. Global symbols like ·mask are visible throughout the entire program and must be unique. Local symbols like `mask<>` are only visible within their own file and can be defined in each file without causing conflicts.