Merge branch 'master' of github.com:Hacker0x01/docs.hackerone.com

stacyspiva · stacyspiva · commit f81f4f6643a2 · 2020-08-27T15:37:37.000-07:00
diff --git a/docs/programs/good-program.md b/docs/programs/good-program.md
@@ -13,12 +13,12 @@ Programs that engage in [disclosure](disclosure.html) find themselves having hig
 [Set your response targets](setting-response-targets.html) to fall between the recommended and standard response times. The faster your response times, the higher likelihood of hackers engaging with your program as they’ll see that you’re actively responding to reports.  
 
 ### Tip #3: Communicate with your hackers
-It’s best practice to actively [communicate with your hackers](communicating-with-hackers.html) by commenting on reports and answering any questions or concerns they have in a timely manner and letting them know of any updates or changes to your program by using the [message hackers](programs/message-hackers.html) feature.
+It’s best practice to actively [communicate with your hackers](communicating-with-hackers.html) by commenting on reports and answering any questions or concerns they have in a timely manner and letting them know of any updates or changes to your program by using the [message hackers](message-hackers.html) feature.
 
 ### Tip #4: Utilize Bounty Tables
-Set up [bounty tables](programs/bounty-tables.html) as they help hackers to see how much is rewarded based on the severity level of the vulnerability.  Additionally, it’s important that you set your bounties to fair amounts that don’t underpay hackers.  
+Set up [bounty tables](bounty-tables.html) as they help hackers to see how much is rewarded based on the severity level of the vulnerability.  Additionally, it’s important that you set your bounties to fair amounts that don’t underpay hackers.  
 
 ### Tip #5: Keep your policy up-to-date
-Make sure all helpful and important information is written on your [policy](policy-and-scope.html) and that you follow the [best practices for good policies](programs/good-policies.html).
+Make sure all helpful and important information is written on your [policy](policy-and-scope.html) and that you follow the [best practices for good policies](good-policies.html).
 
 Keep in mind that these short tips don’t guarantee success for your program, but they do help in increasing engagement with hackers. There are a lot of other factors that can affect the success of your program such as the types of assets, the bounty amounts,
diff --git a/docs/programs/sso-faqs.md b/docs/programs/sso-faqs.md
@@ -14,5 +14,7 @@ Is SAML configurable on a per user basis? | No, all users belonging to a SAML en
 Do you support custom session times? | Yes, HackerOne will respect the SessionNotOnOrAfter attribute if provided during authentication. This will allow you to customize the length of the session up to an upper bound of 2 weeks. If you provide this value, it'll be the source of truth and the *remember me* will be ignored.
 Do you support Single Logout? | No, we don't support single logout at this time.
 What happens to users on my team that don't belong to our claimed domain? | Turning on SSO will only affect users of the claimed domain. Any users that are using e-mail addresses on other domains will not be affected.
+What is your NameID format? | `urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress`
 What is your Entity ID? | hackerone.com
 What is your ACS URL? | https://hackerone.com/users/saml/auth
+What are your attribute fields? | `User.firstName` (First Name) and `User.lastName` (Last Name). You can read more details about what is available [here](/programs/sso-jit.html).
diff --git a/src/pages/programs/programs-nav.yaml b/src/pages/programs/programs-nav.yaml
@@ -17,7 +17,7 @@
       path: /programs/passwords.html
     - title: Using Markdown
       path: /programs/using-markdown.html
-    - title: Running a Good Prgram
+    - title: Running a Good Program
       path: /programs/good-program.html
 - title: Your Program
   items:
