aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--documentation/content/en/books/handbook/wine/_index.adoc3
1 files changed, 2 insertions, 1 deletions
diff --git a/documentation/content/en/books/handbook/wine/_index.adoc b/documentation/content/en/books/handbook/wine/_index.adoc
index 9e90f1b12f..8d216ed495 100644
--- a/documentation/content/en/books/handbook/wine/_index.adoc
+++ b/documentation/content/en/books/handbook/wine/_index.adoc
@@ -59,7 +59,8 @@ It will also translate any responses as needed into what the Windows(R) software
So in some ways, it _emulates_ a Windows(R) environment, in that it provides many of the resources Windows(R) applications are expecting.
However, it is not an emulator in the traditional sense.
-Many of these solutions operate by constructing an entire other computer using software processes in place of hardware Virtualization (such as that provided by the package:emulators/qemu[] port) operates in this way.
+Many of these solutions operate by constructing an entire other computer using software processes in place of hardware.
+Virtualization (such as that provided by the package:emulators/qemu[] port) operates in this way.
One of the benefits of this approach is the ability to install a full version of the OS in question to the emulator.
It means that the environment will not look any different to applications than a real machine, and chances are good that everything will work on it.
The downside to this approach is the fact that software acting as hardware is inherently slower than actual hardware.