From bc43457cf072c69e41b48fee4c10a505a6ea9661 Mon Sep 17 00:00:00 2001
From: elagergren-spideroak
 <36516532+elagergren-spideroak@users.noreply.github.com>
Date: Thu, 6 Sep 2018 16:03:56 -0700
Subject: [PATCH] Updated LockOSThread (markdown)

---
 LockOSThread.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/LockOSThread.md b/LockOSThread.md
index dc1fc870..264b5a5d 100644
--- a/LockOSThread.md
+++ b/LockOSThread.md
@@ -1,6 +1,6 @@
 # Introduction
 
-Some libraries—especially graphical frameworks and libraries like Cocoa, OpenGL, and libSDL—use thread-local state and can require functions to be called only from a specific OS thread, typically the 'main' thread. Go's runtime package provides the `LockOSThread()` function for this, but it's notoriously difficult to use correctly.
+Some libraries—especially graphical frameworks and libraries like Cocoa, OpenGL, and libSDL—use thread-local state and can require functions to be called only from a specific OS thread, typically the 'main' thread. Go provides the `runtime.LockOSThread` function for this, but it's notoriously difficult to use correctly.
 
 # Solutions