Hi,
The use of <b></b>-tags around make commands in the Porting Guide looks
inconsistent to me. Maybe there's a convention I'm not aware of, I
apologize for the noise then.

I'm familiar with the porting checklist but being able to visually scan
the checklist in order to make sure I haven't missed any of the
mandatory make commands would be valuable. However, some of the
bold-tags where removed in r1.55 in order to make the formatting
consistent with the main FAQ-style. Here's a patch to remove the
remaining bold-tags, assuming this is the preferred convention.

Index: guide.html
===================================================================
RCS file: /cvs/www/faq/ports/guide.html,v
retrieving revision 1.67
diff -u -p -r1.67 guide.html
--- guide.html  25 Mar 2017 19:07:05 -0000      1.67
+++ guide.html  1 Apr 2017 17:26:17 -0000
@@ -179,7 +179,7 @@ Don't set <tt>DISTNAME</tt> to point to 
 
 <li>
 You can check to see if you have filled these values in correctly by typing
-<tt><b>make fetch-all</b></tt>.
+<tt>make fetch-all</tt>.
 </ul>
 
 <p>
@@ -270,8 +270,8 @@ supplementary files that the casual user
 </ul>
 
 <br><li>
-Create a checksum in <tt>distinfo</tt> by typing <tt><b>make makesum</b></tt>.
-Then verify the checksum is correct by typing <tt><b>make checksum</b></tt>.
+Create a checksum in <tt>distinfo</tt> by typing <tt>make makesum</tt>.
+Then verify the checksum is correct by typing <tt>make checksum</tt>.
 
 <ul><li>
 In some rare cases, files checksums can't be verified reliably.
@@ -736,9 +736,8 @@ the dependency, try to use it, and fail 
 <dt>Check run-time dependencies versus build-dependencies
 <dd>
 Update your packing-list with make plist.
-Use <tt><b>make port-lib-depends-check</b></tt> to see what libraries your
-software needs (that will end up in <tt>LIB_DEPENDS</tt> or <tt>WANTLIB</tt>,
-usually).
+Use <tt>make port-lib-depends-check</tt> to see what libraries your software
+needs (that will end up in <tt>LIB_DEPENDS</tt> or <tt>WANTLIB</tt>, usually).
 Identify various files and binaries in the dependencies that have to be present
 for the port to work.
 </dl>

Reply via email to