From 5b250ff1214b8199313d5b03067c408c4aed838d Mon Sep 17 00:00:00 2001 From: Mary Hardy Date: Wed, 6 May 2026 16:25:45 -0700 Subject: [PATCH] Clarify compliance issue resolution process Updated terminology from 'compliance tickets' to 'compliance issues' for clarity. This is the only mention of "tickets" --- ...enting Open Source License Compliance Management (LFC194).md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/OpenChain-Training/en/Online-Training-Courses/LFC194 Course Content/Implementing Open Source License Compliance Management (LFC194).md b/OpenChain-Training/en/Online-Training-Courses/LFC194 Course Content/Implementing Open Source License Compliance Management (LFC194).md index f617570..06cee67 100644 --- a/OpenChain-Training/en/Online-Training-Courses/LFC194 Course Content/Implementing Open Source License Compliance Management (LFC194).md +++ b/OpenChain-Training/en/Online-Training-Courses/LFC194 Course Content/Implementing Open Source License Compliance Management (LFC194).md @@ -590,7 +590,7 @@ It can be prevented by enforcing periodic audits and providing proper staffing t #### Failure to resolve audit findings -This type of failure can be avoided by not allowing compliance tickets to be resolved or closed if the audit report is not finalized. +This type of failure can be avoided by not allowing compliance issues to be resolved or closed if the audit report is not finalized. It can be prevented by implementing blocks in approvals in the open source compliance process. For example, a product cannot be shipped until acceptable compliance is achieved according to the Organization’s policy.