added following hackers to yaml file

stacyspiva · stacyspiva · commit 42f624b11d52 · 2020-04-03T14:01:32.000-07:00
diff --git a/docs/programs/locking-reports.md b/docs/programs/locking-reports.md
@@ -18,7 +18,7 @@ You can only lock closed reports. Program members with report management permiss
 
 ![lock-report](./images/lock-report.png)
 
-After a report has been locked, the hacker can no longer comment on the report, but can still request or agree to public disclosure or request mediation. Your program team members can still comment both publicly and privately on the report. 
+After a report has been locked, the hacker can no longer comment on the report or add a hacker summary, but can still request or agree to public disclosure or request mediation. Your program team members can still comment both publicly and privately on the report.
 
 ![lock-report-2](./images/lock-report-2.png)
 
diff --git a/docs/programs/report-actions.md b/docs/programs/report-actions.md
@@ -47,6 +47,8 @@ To close a report:
 
 ![report-action-3](./images/report-actions-3.png)
 
+***Note:*** *Reports that have gone through [Human-Augmented Signal](human-augmented-signal.html) can be reopened by the hacker if closed*
+
 ### Change the State
 You can change the state of a report to be marked as either *triaged* or *new*. This'll help you keep track of what state your report is in.
 
diff --git a/src/pages/hackers/hackers-nav.yaml b/src/pages/hackers/hackers-nav.yaml
@@ -34,6 +34,8 @@
           path: /hackers/external-payments.html
         - title: Payments FAQs
           path: /hackers/payments-faqs.html
+    - title: Following
+      path: /hackers/following.html
     - title: Notifications
       path: /hackers/manage-notifications.html
     - title: Background Checks
