diff --git a/_pages/implement/go.md b/_pages/implement/go.md
index d77ee37..7ffcb8d 100755
--- a/_pages/implement/go.md
+++ b/_pages/implement/go.md
@@ -19,6 +19,8 @@ sidebar:
 
 {% include toc icon="file-text" %}
 
+The following is an excerpt from 2018 by Dr. Brandon Wiley, The Operator Foundation
+
 Transports that implement the PT 2.0 Go API (see the [PT2 spec](/spec/)) provide a “virtual network interface” that can be used instead of Go’s net.Conn API for sending and receiving traffic over the network. When using these transports, the application data is transformed so as to be resistant to blocking.
 
 Before we get started writing code, let’s look at the required interfaces. These interfaces can be found in the PT 2.0 Go API specification, as well as in the [*shapeshifter-transports*](https://github.com/OperatorFoundation/shapeshifter-transports) Go library (in the [*base*](https://github.com/OperatorFoundation/shapeshifter-transports/blob/master/transports/base/base.go) package).
@@ -214,4 +216,9 @@ This creates a new variable “buffer” and allocates an array of 1024 bytes wh
 
 ---
 
+## PT API 3.0: How to Use Pluggable Transports in Your Go Application
+
+The most recent version of the Pluggable Transports specification, version 3.0 as of 2023, counts with an available sample implementation for the Go language, which can be found [here](https://github.com/Pluggable-Transports/Pluggable-Transports-spec/blob/main/releases/PTSpecV3.0/Pluggable%20Transport%20Specification%20v3.0%20-%20Go%20Transport%20API%20v3.0.md)
+
+
 *CC-BY Dr. Brandon Wiley, The Operator Foundation*