From 8d405b265285c368df2e9cf1c14acee7532e0ee7 Mon Sep 17 00:00:00 2001
From: nancy.liao <huihui.liao@greentest.com.cn>
Date: 周四, 29 5月 2025 18:14:38 +0800
Subject: [PATCH] Merge branch 'develop' of http://139.9.88.116:3000/r/module/open-license-manager into develop

---
 doc/usage/issue-licenses.md |    9 +++++----
 1 files changed, 5 insertions(+), 4 deletions(-)

diff --git a/doc/usage/issue-licenses.md b/doc/usage/issue-licenses.md
index b977bbe..83a7347 100644
--- a/doc/usage/issue-licenses.md
+++ b/doc/usage/issue-licenses.md
@@ -1,7 +1,7 @@
 # Issue licenses
 
 The easiest way to issue licenses is to enter the project library and create the following project structure:
-The projects folder can be anyware. We created one in `open-license-manager/projects` for your convenience (and for testing purposes). A default project<sup>1</sup> named `DEFAULT` has been created for you when you configured the project with cmake.
+The projects folder can be anyware. We created one in `licensecc/projects` for your convenience (and for testing purposes). A default project<sup>1</sup> named `DEFAULT` has been created for you when you configured the project with cmake.
 You can re-configure the project with the `LCC_PROJECT_NAME` cmake variable to create a new project.
  
 ```
@@ -39,10 +39,10 @@
 Once you have the hardware identifier you can issue the command:
 
 ```
-cd projects/DEFAULT #(or whatever your project name is) 
+cd projects/DEFAULT #(or whatever your `lcc-project` is) 
 lcc license issue --client-signature XXXX-XXXX-XXXX -o licenses/{license-file-name}.lic
 ```
-usually this command is issued in the host machine where you compiled `licensecc`
+to create the license file (usually this command is issued in the host machine where you compiled `licensecc`).
 
 ## Full set of options
 A good way to start exploring available options is the command: `lcc license issue --help`
@@ -58,4 +58,5 @@
 |feature-names     | Comma separated list of features to license. See `multi-feature` discussion.               |
 
 Note:
-<sup>1</sup> a project is a container for the customizations of open-license-manager. In special way its keys and build parameters. The name should reflect the name of the software you want to add a license to. The project name appears in the license file.
\ No newline at end of file
+<sup>1</sup> a project is a container for the customizations of licensecc. In special way its keys and build parameters. 
+The name should reflect the name of the software you want to add a license to. The project name appears in the license file.
\ No newline at end of file

--
Gitblit v1.9.1