diff --git a/README.md b/README.md
index 2d51aba..49eeb40 100644
--- a/README.md
+++ b/README.md
@@ -1204,7 +1204,7 @@ func main() {
 
 We are no longer triggering a panic and can now use the `NullWriter` as a `Writer`. This initialisation process is not much different from having properties that are initialised as `nil`, as discussed previously. Therefore, logically, we should try to handle them in a similar way. However, this is where embedded interfaces become a little difficult to work with. In a previous section, it was explained that the best way to handle potential `nil` values is to make the property in question private and create a public *getter* method. This way, we could ensure that our property is, in fact, not `nil`. Unfortunately, this is simply not possible with embedded interfaces, as they are by nature always public.
 
-Another concern raised by using embedded interfaces, is the potential confusion caused by partially overwritten interface methods: 
+Another concern raised by using embedded interfaces is the potential confusion caused by partially overwritten interface methods: 
 
 ```go
 type MyReadCloser struct {