From 9afdac17dcc8956fd795797bfc5b6e1c09285342 Mon Sep 17 00:00:00 2001
From: Gabriele Contini <contini.mailing@gmail.com>
Date: 周日, 08 3月 2020 21:27:16 +0800
Subject: [PATCH] Issues #14 and #6

---
 doc/Hardware-identifiers.md |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/doc/Hardware-identifiers.md b/doc/Hardware-identifiers.md
index 1967f3f..7a18fe6 100644
--- a/doc/Hardware-identifiers.md
+++ b/doc/Hardware-identifiers.md
@@ -7,7 +7,7 @@
 This is straightforward case. If the software is executing on a physical hardware it is possible to identify the hardware by various parameters (cpu type/memory/disk label/mac address)
 
 ### Execution in a virtual machine
-Generating a pc identifier on a virtual machine doesn't make much sense, since the vm can be copied as a whole elsewhere 
+Generating a hardware identifier on a virtual machine doesn't make much sense, since the vm can be copied as a whole elsewhere 
 and there are few ways to detect this without using an external license server.
 
 *   Usually when the machine is copied the MAC address is changed. But sometimes it changes on its own. Software publishers may want to use this as a last resort to prevent the vm for being cloned. It has to be verified case by case.

--
Gitblit v1.9.1