From 945ef8961cfab9afbd73c434bd557ea5074d46b3 Mon Sep 17 00:00:00 2001
From: gritbub <38131016+gritbub@users.noreply.github.com>
Date: Tue, 5 Jun 2018 17:03:51 -0500
Subject: Fix typo

@gwtnb opened PR 597 while PR 591 was still open, pointing out this
typo that had been missed.

Incorporate this typo fix into PR 591
---
 doc/using/QuickStartGuide.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/using/QuickStartGuide.rst b/doc/using/QuickStartGuide.rst
index 974d550ac..279969db1 100644
--- a/doc/using/QuickStartGuide.rst
+++ b/doc/using/QuickStartGuide.rst
@@ -48,7 +48,7 @@ To illustrate the general purpose of `VHDL`, here is a commented `'Hello world'`
    If a GCC/LLVM variant of `GHDL` is used:
 
    * `Analysis` generates a file, :file:`hello.o`, which is the object file corresponding to your `VHDL` program. This is not created with mcode.
-   * The elaboration step is mandatory after running the analysis and prior to launching the simulation. This wil generate an executable binary named :file:`hello_world`.
+   * The elaboration step is mandatory after running the analysis and prior to launching the simulation. This will generate an executable binary named :file:`hello_world`.
    * As a result, :option:`-r` is just a passthrough to the binary generated in the `elaboration`. Therefore, the executable can be run directly, ``./hello_world``. See :option:`-r` for more informartion.
 
 .. HINT:: :option:`-e` can be bypassed with mcode, since :option:`-r` actually elaborates the design and saves it on memory before running the simulation. But you can still use it to check for some elaboration problems.
-- 
cgit v1.2.3