Code have been checked with spec

[mirror_edk2.git] / MdePkg / Include / Protocol / GuidedSectionExtraction.h

diff --git a/MdePkg/Include/Protocol/GuidedSectionExtraction.h b/MdePkg/Include/Protocol/GuidedSectionExtraction.h
index 7c95b1a4b4a535839c8788428c4bd1b14e8a32ce..adeecc043ca63754f22def111d0d955ae5ef839a 100644 (file)
--- a/MdePkg/Include/Protocol/GuidedSectionExtraction.h
+++ b/MdePkg/Include/Protocol/GuidedSectionExtraction.h
@@ -126,18 +126,13 @@ EFI_STATUS
 );\r
 \r
 \r
-/**\r
-  @par Protocol Description:\r
-  Typically, protocol interface structures are identified by associating them with a GUID. Each\r
-  instance of a protocol with a given GUID must have the same interface structure. While all instances\r
-  of the GUIDed Section Extraction Protocol must have the same interface structure, they do not all\r
-  have the same GUID. The GUID that is associated with an instance of the GUIDed Section\r
-  Extraction Protocol is used to correlate it with the GUIDed section type that it is intended to process.\r
-\r
-  @param ExtractSection\r
-  Takes the GUIDed section as input and produces the section stream data.\r
-\r
-**/\r
+///\r
+/// Typically, protocol interface structures are identified by associating them with a GUID. Each\r
+/// instance of a protocol with a given GUID must have the same interface structure. While all instances\r
+/// of the GUIDed Section Extraction Protocol must have the same interface structure, they do not all\r
+/// have the same GUID. The GUID that is associated with an instance of the GUIDed Section\r
+/// Extraction Protocol is used to correlate it with the GUIDed section type that it is intended to process.\r
+///\r
 struct _EFI_GUIDED_SECTION_EXTRACTION_PROTOCOL {\r
   EFI_EXTRACT_GUIDED_SECTION  ExtractSection;\r
 };\r