Fix image URLs; missing path prefix (#62)

docs/actions.md

@@ -35,7 +35,7 @@ Zipped actions are usually created in a separate build step. As an alternative,
 
 By creating a directory under the package directory, named for the action, and containing its source file(s), you can expand to multiple source files and they will be zipped automatically. Certain conditions must be met for this to work. Suppose the [example1 project](single-action-example.md) has a `hello` action with two source files: _helloMain.js_ and _helloAux.js_. To create the `demo/hello` action, add a `hello` directory as a child of the `demo` directory, as shown in this diagram.
 
-<center><img src="img/fig4-nim-example2-project-directory-structure.svg" height="450"/></center>
+<center><img src="/img/fig4-nim-example2-project-directory-structure.svg" height="450"/></center>
 <center><strong>Figure 3: Two source files in an action directory for automatic zipping</strong></center>
 
 The difference from the [example1 directory structure](single-action-example.md#fig2) is that the `hello` action is a _directory_ rather than a single source file. The source files in the directory are zipped automatically to form the action.
@@ -51,7 +51,7 @@ These conditions can be relaxed by using [project configuration](configuration.m
 
 Subdirectories can be present under an action directory (for example, a `node_modules` directory as in the following diagram). These directories are zipped up with everything else under the action directory.
 
-<center><img src="img/fig5-nim-example2-complex-directory-structure.svg" height="450"/></center>
+<center><img src="/img/fig5-nim-example2-complex-directory-structure.svg" height="450"/></center>
 <center><strong>Figure 4: Autozipping a subdirectory of an action directory</strong></center>
 
 You can optionally limit the files to be zipped in either of two ways:

docs/configuration.md

@@ -180,7 +180,7 @@ It is important is that the initial token `$(` be placed somewhere where the YAM
 
 Here’s an example of a basic _web_ directory structure when you use a tool to generate web content. Chances are the tool puts its output in a specific directory. Here’s an example diagram of the _web_ directory for an `example4` project, using React to generate the web content.
 
-<center><img src="img/fig7-nim-examples-project-chat-react-directory-structure.svg" height="550"/></center>
+<center><img src="/img/fig7-nim-examples-project-chat-react-directory-structure.svg" height="550"/></center>
 <center><strong>Figure 6: Project web directory structure for generated web content</strong></center>
 
 The _web_ directory contains a _.include_ file and some other files related to building not shown in the diagram. The _public_ and _src_ directories contain the source of the React web application. The _build_ directory is generated by the React build and contains all of the content to be deployed.

docs/projects.md

@@ -13,7 +13,7 @@ A project represents a logical unit of functionality whose boundaries are up to
 
 A project has a fixed directory structure, which determines how projects are deployed. Here’s a diagram that summarizes the directory structure of an individual project with no project configuration, with explanation below.
 
-<center><img src="img/fig3-nim-project-directory-structure.svg" height="300"/></center>
+<center><img src="/img/fig3-nim-project-directory-structure.svg" height="300"/></center>
 <center><strong>Figure 2: Basic directory structure of a project</strong></center>
 
 The project has a root directory, within which a certain small number of directory names are significant to the deployer, specifically:

docs/single-action-example.md

@@ -96,7 +96,7 @@ Deployed actions:
 
 Here’s a diagram of the project structure that was created in this procedure.
 
-<center id="fig2"><img src="img/fig2-nim-example1-project-directory-structure.svg" height="300"/></center>
+<center id="fig2"><img src="/img/fig2-nim-example1-project-directory-structure.svg" height="300"/></center>
 <center><strong>Figure 1: Directory structure of the example1 project</strong></center>
 
 **Notes:**

docs/web-content.md

@@ -27,7 +27,7 @@ example3/web/favicon.ico
 
 Here’s a diagram of the `example3` project structure.
 
-<center><img src="img/fig6-nim-example3-project-directory-structure.svg" height="450"/></center>
+<center><img src="/img/fig6-nim-example3-project-directory-structure.svg" height="450"/></center>
 <center><strong>Figure 5: A project with static web content</strong></center>
 
 Here’s the output when the project is deployed.