Date: Sat, 15 Jul 2017 05:08:43 -0700
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: [PATCH 1/2] future/QC: Fix typos
Reply-To: paulmck@linux.vnet.ibm.com
References: <20170713231923.4929-1-sj38.park@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170713231923.4929-1-sj38.park@gmail.com>
Message-Id: <20170715120843.GB2393@linux.vnet.ibm.com>
Sender: perfbook-owner@vger.kernel.org
To: SeongJae Park <sj38.park@gmail.com>
Cc: perfbook@vger.kernel.org

On Fri, Jul 14, 2017 at 08:19:22AM +0900, SeongJae Park wrote:
> Signed-off-by: SeongJae Park <sj38.park@gmail.com>

Good eyes, both applied, thank you!

							Thanx, Paul

> ---
>  future/QC.tex | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/future/QC.tex b/future/QC.tex
> index d16c080..f985437 100644
> --- a/future/QC.tex
> +++ b/future/QC.tex
> @@ -411,7 +411,7 @@ ten digits of precision.
>  If this was all that QC provided, QC would be a rather slow and very
>  low-quality analog computer.
>  Given that digital computers obsoleted analog computers some decades back,
> -This analogy might lead many developers to ignore QC and to
> +this analogy might lead many developers to ignore QC and to
>  use classic-computing floating point instead.
>  However, QC provides a powerful capability covered in the next section.
> 
> @@ -798,7 +798,7 @@ For example, perhaps machine-learning techniques will allow difficult
>  cases to be detected so that alternative solution methods can be applied
>  as needed.
> 
> -Of course, much of this work has been heuristic and/or probabalistic,
> +Of course, much of this work has been heuristic and/or probabilistic,
>  so it might at first glance seem unfair to compare them to
>  QC algorithms.
>  However, QC algorithms are inherently probabilistic due to error rates
> -- 
> 2.10.0
>