Forwarding rule bugfix

DEVELOPER.md

@@ -83,6 +83,10 @@ Optional fields:
    corresponding API property we can use `field` to map the user facing name
    (specified by the `name` parameter) to the backend API (specified by the
    `field` parameter)
+-  `resource`: A resource this resource is dependent upon. See
+   [Api::Type::ResourceRef](#resource-ref).
+-  `imports`: An imported property from the dependent resource specified by
+   `resource`. See [Api::Type::ResourceRef](#resource-ref).
 
 Example:
 
@@ -157,7 +161,7 @@ Currently MM supports the following types:
 -  Api::Type::NameValues
 -  `Api::Type::NestedObject`: A composite field, composed of inner fields. This
    is used for structures that are nested.
--  `Api::Type::ResourceRef`: A reference to another object described in the
+-  <a id="resource-ref"></a>`Api::Type::ResourceRef`: A reference to another object described in the
    product. This is used to create strong relationship binding between the
    objects, where the generated code will make sure the object depended upon
    exists. A `ResourceRef` also specifies which property from the dependent

README.md

@@ -112,6 +112,16 @@ We are now ready to compile a module!
 
 ## Compiling modules
 
+### Prerequisites
+
+Each module has its own set of prerequisites for successful compilation. It is
+advisable to read the documentation within a particular module's project
+repository before attempting compilation to ensure prerequisites are installed.
+A list of each module's repository URL can be retrieved via the following
+command:
+
+	git config --file .gitmodules --get-regexp url
+
 ### Compiling a single module
 
 Compiling a module is as easy as: