faq/ports/guide.html: plist -> update-plist

update-plist(1) landed some time ago, Marc send a couple of mails to
ports@ talking about it and general advise is to just use that, so
update our guide accordingly.

Also, only the `update-plist' target is documented in bsd.port.mk(5)
while `plist' is not.

Feedback? OK?

Index: faq/ports/guide.html
===================================================================
RCS file: /cvs/www/faq/ports/guide.html,v
retrieving revision 1.84
diff -u -p -r1.84 guide.html
--- faq/ports/guide.html 18 Sep 2018 08:04:03 -0000 1.84
+++ faq/ports/guide.html 2 Dec 2018 16:43:42 -0000
@@ -553,7 +553,7 @@ For automatic updating of <code>/etc</co
<br><br><li>
Create <code>pkg/PLIST</code>.
After the installation with <code>make fake</code> is complete, use the
-developer's command <code>make plist</code>, which creates or updates
+developer's command <code>make update-plist</code>, which creates or updates
the file <code>PLIST</code> in the <code>pkg</code> directory.
This file is a candidate packing list.

@@ -569,7 +569,7 @@ Note that <code>PLIST</code> annotations
It is possible some directories do not need to be in the <code>PLIST</code>
as they've been installed by a dependency;
if you added to <code>LIB_DEPENDS</code> or <code>RUN_DEPENDS</code>,
-re-run <code>make plist</code> to remove these.
+run <code>make update-plist</code> to remove these.

<br><br><li>
Test the packaging with <code>make package</code>, test installation of the
@@ -732,7 +732,7 @@ and import it, and soon after, old ports
the dependency, try to use it, and fail to build or package.
<dt>Check run-time dependencies versus build-dependencies
<dd>
-Update your packing-list with <code>make plist</code>.
+Update your packing-list with <code>make update-plist</code>.
Use <code>make port-lib-depends-check</code> to see what libraries your
software needs
(that will end up in <code>LIB_DEPENDS</code> or <code>WANTLIB</code>, usually).