Updated Add a New Package: Full Version (markdown)

Add-a-New-Package:-Full-Version.md

@@ -10,7 +10,7 @@ A package recipe usually contain the following:
 | `$(PKG)_SUBDIR`                | The real root source tree inside `$(PKG)_URL`
 | `$(PKG)_FILE`                  | Name of the tarball or zip archive.
 | `$(PKG)_URL`                   | URL of the tarball or zip archive.
-| `$(PKG)_DEPS`                  
+| `$(PKG)_DEPS`                  | Dependencies of this package. Non-toolchain packages should always contain gcc.
 
 ## `$(PKG)_BUILD` macro
 The `$(PKG)_BUILD` macro shall take 2 parameters that will be called with
@@ -21,14 +21,14 @@ the root of the source tree. It shall also be `mxe/tmp-$(PKG)/$($(PKG)_SUBDIR)`.
 
 The second parameter, accessible with `$(2)`, shall always be `src/$(PKG)-test`.
 
-In the macro, the package shall be built and installed. There shall be 3 types
+In the macro, the package will be built and installed. There shall be 3 types
 of packages:
 
 1. The package is library-only, or with an "example program". In this case, the
    "example program" shall not be essential to the use of the library, and the
    building and installation of the example program should be disabled, if
    possible.
-> Example: package `a52dec`
+> Examples: packages `a52dec` and `ffmpeg`
 
 The installation of the
 library that will be used for the target shall be under `$(PREFIX)/$(TARGET)`.
@@ -76,4 +76,4 @@ endef
 $(PKG)_BUILD_i686-pc-mingw32    = $(subst @special-target@, x86-win32-gcc,    $($(PKG)_BUILD))
 $(PKG)_BUILD_i686-w64-mingw32   = $(subst @special-target@, x86-win32-gcc,    $($(PKG)_BUILD))
 $(PKG)_BUILD_x86_64-w64-mingw32 = $(subst @special-target@, x86_64-win64-gcc, $($(PKG)_BUILD))
-```
+```