Use doxygen comment style for document entity such as struct, enum, variable that...

[mirror_edk2.git] / MdePkg / Include / Guid / FirmwareFileSystem2.h

diff --git a/MdePkg/Include/Guid/FirmwareFileSystem2.h b/MdePkg/Include/Guid/FirmwareFileSystem2.h
index 4a3adbb03dac6319db68bb3120b8fc81bd0ee070..383f24ff8f5d2380b24a9a674c09968d833d9f3c 100644 (file)
--- a/MdePkg/Include/Guid/FirmwareFileSystem2.h
+++ b/MdePkg/Include/Guid/FirmwareFileSystem2.h
@@ -18,18 +18,18 @@
 #ifndef __FIRMWARE_FILE_SYSTEM2_GUID_H__\r
 #define __FIRMWARE_FILE_SYSTEM2_GUID_H__\r
 \r
-// \r
-// The firmware volume header contains a data field for \r
-// the file system GUID\r
-// \r
+/// \r
+/// The firmware volume header contains a data field for \r
+/// the file system GUID\r
+/// \r
 #define EFI_FIRMWARE_FILE_SYSTEM2_GUID \\r
   { 0x8c8ce578, 0x8a3d, 0x4f1c, { 0x99, 0x35, 0x89, 0x61, 0x85, 0xc3, 0x2d, 0xd3 } }\r
 \r
-//\r
-// A Volume Top File (VTF) is a file that must be \r
-// located such that the last byte of the file is \r
-// also the last byte of the firmware volume\r
-// \r
+///\r
+/// A Volume Top File (VTF) is a file that must be \r
+/// located such that the last byte of the file is \r
+/// also the last byte of the firmware volume\r
+/// \r
 #define EFI_FFS_VOLUME_TOP_FILE_GUID \\r
   { 0x1BA0062E, 0xC779, 0x4582, { 0x85, 0x66, 0x33, 0x6A, 0xE8, 0xF7, 0x8F, 0x9 } }\r
 \r