Update

README.rst

@@ -93,12 +93,13 @@ The logical vertex table will be partitioned into multiple continuous vertex chu
 
 Take the "person" vertex table as an example, if the chunk size is set to be 500, the logical table will be separated into sub-logical-tables of 500 rows with the exception of the last one, which may have less than 500 rows. The columns for maintaining properties will also be divided into distinct groups (e.g., 2 for our example). As a result, a total of 4 physical vertex tables are created for storing the example logical table, which can be seen from the following figure.
 
-.. image:: https://alibaba.github.io/GraphAr/_images/vertex_physical_table.png
+# .. image:: https://alibaba.github.io/GraphAr/_images/vertex_physical_table.png
+.. image:: docs/images/vertex_physical_table.png
   :width: 650
   :align: center
   :alt: vertex physical table
 
-Note: For efficiently utilize the filter push-down of the payload file format like Parquet, the internal vertex id is stored in the payload file as a column. And since the internal vertex id is continuous, the payload file format can use the dictionary encoding for the internal vertex id column, which would not bring too much overhead for the storage.
+Note: For efficiently utilize the filter push-down of the payload file format like Parquet, the internal vertex id is stored in the payload file as a column. And since the internal vertex id is continuous, the payload file format can use the delta encoding for the internal vertex id column, which would not bring too much overhead for the storage.
 
 Edges in GraphAr
 ^^^^^^^^^^^^^^^^

docs/user-guide/file-format.rst

@@ -57,7 +57,7 @@ Take the "person" vertex table as an example, if the chunk size is set to be 500
    :alt: vertex physical table
 
 
-Note: For efficiently utilize the filter push-down of the payload file format like Parquet, the internal vertex id is stored in the payload file as a column. And since the internal vertex id is continuous, the payload file format can use the dictionary encoding for the internal vertex id column, which would not bring too much overhead for the storage.
+Note: For efficiently utilize the filter push-down of the payload file format like Parquet, the internal vertex id is stored in the payload file as a column. And since the internal vertex id is continuous, the payload file format can use the delta encoding for the internal vertex id column, which would not bring too much overhead for the storage.
 
 Edges in GraphAr
 ------------------------