From a37ef48570136c83d6de591149efe383eae9e012 Mon Sep 17 00:00:00 2001
From: Daniel Kurzynski <daniel.kurzynski@sap.com>
Date: Wed, 22 Apr 2020 11:25:51 +0200
Subject: [PATCH] Document new identifier (#1392)

---
 documentation/docs/scenarios/CAP_Scenario.md     | 2 +-
 documentation/docs/scenarios/changeManagement.md | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/documentation/docs/scenarios/CAP_Scenario.md b/documentation/docs/scenarios/CAP_Scenario.md
index a353f487a..eefc866bb 100644
--- a/documentation/docs/scenarios/CAP_Scenario.md
+++ b/documentation/docs/scenarios/CAP_Scenario.md
@@ -70,7 +70,7 @@ In this scenario, we want to show how to implement a basic continuous delivery p
 #### Jenkinsfile
 
 ```groovy
-@Library('piper-library-os') _
+@Library('piper-lib-os') _
 
 node(){
   stage('Prepare')   {
diff --git a/documentation/docs/scenarios/changeManagement.md b/documentation/docs/scenarios/changeManagement.md
index 8f8cb2c04..78d3332a5 100644
--- a/documentation/docs/scenarios/changeManagement.md
+++ b/documentation/docs/scenarios/changeManagement.md
@@ -46,7 +46,7 @@ The basic workflow is as follows:
 ### Jenkinsfile
 
 ```groovy
-@Library('piper-library-os') _
+@Library('piper-lib-os') _
 
 node() {