1 files changed, 10 insertions, 2 deletions

diff --git a/docs/creating_a_rock.md b/docs/creating_a_rock.md
index 07de5ca5..a5441ea4 100644
--- a/docs/creating_a_rock.md
+++ b/docs/creating_a_rock.md
@@ -148,6 +148,14 @@ and `5.3`, but not yet-to-be-released `5.4`. There are a few other operators
 for specifying version constraints, see
 [Rockspec format](rockspec_format.md#dependency-information).
 
+Rockspecs from [`rockspec_format = "3.1"`](rockspec_format.md#package-metadata)),
+have access to special variables with the path of the installed rocks of its
+dependencies. See the [section below](#including-documentation-and-other-files)
+for information on how rocks can include files in their installation. Each
+variable is the name of the dependency followed by the suffix `_ROCKDIR`. For
+the example above, variable `LUAKNIFE_ROCKDIR` will be provided with the path of
+the installed rock.
+
 #### C modules linking to external libraries
 
 *If your code does not use third-party libraries, you may skip this subsection.*
@@ -231,7 +239,7 @@ luarocks doc ROCKNAME
 Now, to complete the rockspec for public consumption we need to fill the
 sources.url field. For that, we need the code to be available online. We have
 two approaches for that: if you have your source code in an online repository
-such as [GitHub](GitHub)(https://github.com), you may use that directly.
+such as [GitHub](https://github.com), you may use that directly.
 Alternatively, you can publish a tarball with the sources on the web.
 
 ### Method 1: using a repository such as Github
@@ -315,7 +323,7 @@ tar czvpf luafruits-1.0.tar.gz luafruits-1.0/
 
 And now we're ready to publish the tarball online. You can upload it to any
 public web server; if you need hosting space, you can use the Pages feature
-from [GitHub](GitHub)(https://github.com). Your source section would then look
+from [GitHub](https://github.com). Your source section would then look
 something like this:
 
 ```lua