aboutsummaryrefslogtreecommitdiff
path: root/content/go-at-io-frequently-asked-questions.article
diff options
context:
space:
mode:
Diffstat (limited to 'content/go-at-io-frequently-asked-questions.article')
-rw-r--r--content/go-at-io-frequently-asked-questions.article2
1 files changed, 1 insertions, 1 deletions
diff --git a/content/go-at-io-frequently-asked-questions.article b/content/go-at-io-frequently-asked-questions.article
index 9b7d009..37a09c3 100644
--- a/content/go-at-io-frequently-asked-questions.article
+++ b/content/go-at-io-frequently-asked-questions.article
@@ -33,7 +33,7 @@ Additionally, the more Go code we write (and thus the better we learn how
to write Go code ourselves),
the less we feel the need for such a language feature.
-Do you have any plans to support GPU programming?
+Do you have any plans to support GPU programming?
We don't have any immediate plans to do this,
but as Go is architecture-agnostic it's quite possible.
The ability to launch a goroutine that runs on a different processor architecture,