Fix docs for handling failures in goroutines

docs/css/layout.css

@@ -191,11 +191,11 @@ a:last-of-type .logo {
 	}	
 
 	#left-background {
-		grid-area; left-background;
+		grid-area: left-background;
 	}
 
 	#right-background {
-		grid-area; right-background;
+		grid-area: right-background;
 	}
 
 	#header {

docs/index.md

@@ -1202,15 +1202,32 @@ When a failure occurs in a `BeforeEach`, `JustBeforeEach`, or `It` closure Ginkg
 
 Ginkgo orchestrates this behavior by rescuing the panic thrown by `Fail` and unwinding the spec.  However, if your spec launches a **goroutine** that calls `Fail` (or, equivalently, invokes a failing Gomega assertion), there's no way for Ginkgo to rescue the panic that `Fail` throws.  This will cause the suite to panic and no subsequent specs will run.  To get around this you must rescue the panic using `defer GinkgoRecover()`.  Here's an example:
 
+However, if you block in a test case, Ginkgo will not be able to catch the failure and the case will time out instead.
+
 ```go
+/* === INVALID === */
 It("panics in a goroutine", func() {
   var c chan interface{}
   go func() {
     defer GinkgoRecover()
     Fail("boom")
     close(c)
   }()
-  <-c
+  <-c // Do not block!
+})
+```
+
+[Asynchronous assertions](https://onsi.github.io/gomega/#making-asynchronous-assertions) can be used to wait for the condition while allowing Ginkgo to abort the case when an async failure occurs.
+
+```go
+It("panics in a goroutine", func() {
+  done := make(chan struct{})
+  go func() {
+    defer GinkgoRecover()
+    Fail("boom")
+    close(c)
+  }()
+  Eventually(done).Should(BeClosed())
 })
 ```