diff --git a/Documentation/AdvancedUsage.md b/Documentation/AdvancedUsage.md
index 2df2b24fd..1095681ce 100644
--- a/Documentation/AdvancedUsage.md
+++ b/Documentation/AdvancedUsage.md
@@ -495,7 +495,7 @@ Alamofire provides built-in response serialization for data, strings, JSON, and
 Alamofire.request(...).responseData { (resp: DataResponse<Data>) in ... }
 Alamofire.request(...).responseString { (resp: DataResponse<String>) in ... }
 Alamofire.request(...).responseJSON { (resp: DataResponse<Any>) in ... }
-Alamofire.request(...).responsePropertyList { resp: DataResponse<Any>) in ... }
+Alamofire.request(...).responsePropertyList { (resp: DataResponse<Any>) in ... }
 ```
 
 Those responses wrap deserialized *values* (Data, String, Any) or *errors* (network, validation errors), as well as *meta-data* (URL request, HTTP headers, status code, [metrics](#statistical-metrics), ...).
@@ -936,4 +936,4 @@ There are some important things to remember when using network reachability to d
 - The network reachability status can be useful for determining why a network request may have failed.
     - If a network request fails, it is more useful to tell the user that the network request failed due to being offline rather than a more technical error, such as "request timed out."
 
-> It is recommended to check out [WWDC 2012 Session 706, "Networking Best Practices"](https://developer.apple.com/videos/play/wwdc2012-706/) for more info.
\ No newline at end of file
+> It is recommended to check out [WWDC 2012 Session 706, "Networking Best Practices"](https://developer.apple.com/videos/play/wwdc2012-706/) for more info.