husttle
diff --git a/‎docs/changelog/2022/march.md
Lines changed: 2 additions & 2 deletions b/‎docs/changelog/2022/march.md
Lines changed: 2 additions & 2 deletions
diff --git a/‎docs/programs/asset-based-credential-management.md
Lines changed: 1 addition & 8 deletions b/‎docs/programs/asset-based-credential-management.md
Lines changed: 1 addition & 8 deletions
diff --git a/‎docs/programs/images/asset-based-11.png
-1.34 MB b/‎docs/programs/images/asset-based-11.png
-1.34 MB
diff --git a/‎docs/programs/images/asset-based-table.png
468 KB b/‎docs/programs/images/asset-based-table.png
468 KB
@@ -5,7 +5,7 @@ date: "2022-03"
 ---
 
 ### Retesting Enhancement
-Once a retest is claimed, the tester will now have 72 hours to complete retesting.
+We've update retesting time so the tester will now have 72 hours to complete retesting.
 
 ### Program Hacker Matching Improvement
 We’ve made improvements to our Invitation Engine, using program requirements and customer preferences to match hackers to opportunities, we provide our hacker community with much more personalized recommendations.
@@ -18,4 +18,4 @@ Customers with multiple programs can now manage users from a single page.
 We released fixes and performance optimizations to ensure consistent data between the Statistics page and the [Submissions and Bounty dashboard.](/programs/submissions-bounty-dashboard.html)
 
 ### Team Member Eligibility
-[Team member eligibility settings](./programs/team-member-eligibility.html) allow you to configure a list of email domains that are eligible to join your program. These settings will allow or block a user when accepting an invitation, but will not affect any users that are already a member of the program. You can set team member eligibility regardless of SAML usage.
+[Team Member Eligibility](/programs/team-member-eligibility.html) settings allow you to configure a list of email domains that are eligible to join your program. These settings will allow or block a user when accepting an invitation, but will not affect any users that are already a member of the program. You can set team member eligibility regardless of SAML usage.
@@ -32,14 +32,7 @@ Asset ID | Asset | Assigned To | Username | Password
 Each hacker is allowed to claim one credential. If a hacker needs two logins, such as a regular account and an admin account, then both of those usernames and passwords can be put into the same credential for that hacker to claim. See examples below.
 
 Table appearance:
-
-Asset ID | Asset | Assigned To | Username | Password | Username2 | Password2
------ | ----- | ----- | ----- | ----- | ----- | -----
-|<img width=20/>|<img width=20/>|<img width=20/>|<img width=20/>|<img width=20/>|<img width=20/>|<img width=20/>|
-1 | https://hackerone.com | hacker-john | John | john123 | JohnAdmin | johnadmin123
-2 | https://api.hackerone.com | jacob-123 | Jacob | jingleheimer123 | JacobAdmin | schmidtadmin123
-3 | https://hackerone-attachments.s3.amazonaws.com/ | jane-hacks | Jane | jane123 | JaneAdmin | janeadmin123
-
+![Table displaying how two logins must be set up](./images/asset-based-table.png)
 
 ### Credential Inquiry
 In the first step of Credential Management you will select which flow you need. In case the program needs specific information about the end-user’s environment in order to prepare a set of credentials, you can create a credential inquiry. Via the Credential Management page, the program specifies what information you need from hackers and selects the asset for which the information is required.