followup on bug triage

doc/bugs/Can__39__t_add_remotes_through_the_web_assistant/comment_10_434c3a17d545b0d37aca55d129ddc66b._comment

@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 10"""
+ date="2018-11-05T18:29:07Z"
+ content="""
+@andrew, take a look at the [[contribute]] page,
+bug triage section.
+"""]]

doc/contribute.mdwn

@@ -25,12 +25,20 @@ Many bugs are also filed without enough information
 to reproduce the problem, and need to be tagged moreinfo and a comment
 posted asking the submitter for details.
 
+Once a bug is confirmed to be reproducible, it becomes a lot easier to fix.
+So it's very helpful to highlight such bugs.
+
 Joey spends a lot of time dealing with this kind of bug triage. If you can
-take the time to pick a bug that is not marked as "confirmed" or "moreinfo"
+take the time to pick a bug that is not tagged as "confirmed" or "moreinfo"
 from the list of [[bugs]], try to reproduce it and follow up either
 confirming that the problem exists, or asking the submitter for more info,
 you'll make Joey more productive!
 
+You can add and modify tags by editing the bug's page with this wiki code:
+
+	\[[!taglink confirmed]]
+	\[[!taglink moreinfo]]
+
 ## code contributions
 
 [[download]] the source code, [[build|install/fromsource]] it
@@ -40,9 +48,8 @@ If you know Haskell, git-annex has lots of Haskell code that
 could be improved. See the [[coding_style]] and have at it.
 
 If you don't know Haskell, git-annex has many other coding opportunities.
-You could work to improve the Android port (Java etc) or improve the
-Javascript and CSS of the git-annex webapp, or work on porting libraries
-needed by the Windows port.
+You could work to improve the Javascript and CSS of the git-annex webapp,
+or work on porting libraries needed by the Windows port.
 
 To send patches, either include the patch in a [[bug|bugs]] report (small
 patch) or put up a branch in a git repository containing your changes.