The pointer to avoid multiple path to accomplish the goal of the get stated guide is very good. It's hard to figure out for what part of the documentation this issue really was. The documentation has also changed since then.

(In reply to comment #0)
> Users do not notice that some parts of the install documentation provide
> multiple options on how to
> accomplish a task. Instead, they think that the actions need to occur
> serially, like the rest of the
> documentation. Find a way to clarify this that can be applied throughout the
> install document and
> implement the changes.
>

Can you clarify this further? Are you speaking of the quick starts? Generally, if someone is doing something for the first time, you need to give them linear instructions or they just walk away. Reading a doc is a linear process, so the instructions in it should also be linear, especially in the case of a "quick start" where someone may not be familiar enough with something like PostgreSQL to be fiddling with stored procedures later.

moving to 1.6.1 target milestone; only things left pending for 1.6.0 are blocker-level bugs