OnBoarding-Procedures.md

@@ -101,14 +101,14 @@ Offboarding process right now for Staff that resigns or are laid off:
  7. If person is core contributor, HR checks with employee if they will continue contributing to the project as a core volunteer and in which area. At this point forward, the person's tor-internal membership will be subject to the Community membership audit process.
  8. If the person was a core contributor before becoming an employee or contractor and is terminated (fired), TPI and the Community Council will coordinate to decide whether the person should remain on tor-internal. (https://gitweb.torproject.org/community/policies.git/tree/membership.txt#n116) https://gitlab.torproject.org/tpo/team/-/wikis/Onboarding-Procedures#termination
  8. If they are not core contributor or do not volunteer: 
-   1. HR creates a ticket in tpo/web/tpo to remove employee from the people page
-   2. Team lead creates a confidential ticket in TPA to remove permissions.
-   3. Remove from all private mailing lists and aliases.
-   4. Disposition of employee's email
+    1. HR creates a ticket in tpo/web/tpo to remove employee from the people page
+    2. Team lead creates a confidential ticket in TPA to remove permissions.
+    3. Remove from all private mailing lists and aliases.
+    4. Disposition of employee's email
  9. If they will volunteer: 
-   1. Team lead creates a ticket in TPA to remove permissions not associated with the area they will continue volunteering with.
-   2. Remove from tor-employees mailing lists.
-   3. Check if they are a security liaison (i.e. on the security@ list), and if so go through the removal process.
+    1. Team lead creates a ticket in TPA to remove permissions not associated with the area they will continue volunteering with.
+    2. Remove from tor-employees mailing lists.
+    3. Check if they are a security liaison (i.e. on the security@ list), and if so go through the removal process.
 
 ### Gets terminated (fired)