Update README.md

README.md

@@ -24,5 +24,6 @@ Each zip file when unzipped generates the folders corresponding to its object cl
 Within each '[classID]/[objectID]/models' subfolder, models are stored as triangular meshes in the PLY file format (https://gamma.cs.unc.edu/POWERPLANT/papers/ply.pdf) as follows: 
 - The waterproofed version of the original model is provided in the file 'model_c.ply', where 'c' stands for complete. 
 - Fragments generated from the fractured (i.e. 'broken') model mesh are stored as 'model_r_[N]\_fragment\_[M].ply', ere, 'b' stands for 'broken', N E {0,1,...,N_max-1} represents the index for the N+1th fractured mesh, and M E {0,1,...} represents the index for the M+1th fragment in decreasing order of volume. N_max is 3 for jars and bottles, 10 for mugs, and 1 for the rest of the classes. The fragment 'model_b_[N]\_fragment\_0.ply' represents the broken mesh fragment with the largest volume.
-- Fragments generated from the repair mesh are stored as 'model_r_[N]\_fragment\_[M].ply', where, 'r' stands for 'repair' and M E {0,1,...} represents the index for the M+1th repair mesh fragment. It should be noted that the number of repair mesh fragments typically differs from the number of broken mesh fragments. 
+- Fragments generated from the repair mesh are stored as 'model_r_[N]\_fragment\_[M].ply', where, 'r' stands for 'repair' and M E {0,1,...} represents the index for the M+1th repair mesh fragment. It should be noted that the number of repair mesh fragments typically differs from the number of broken mesh fragments.
+- 
 In the interest of storage, the original broken and repair meshes generated from subtraction (i.e., the meshes prior to fragmenting connecting components) are not shared. However, they can be generated as a union of the corresponding mesh's fragments.