From d73bb5d287e4e18bd7be4d689b9a86382fa3de3d Mon Sep 17 00:00:00 2001
From: Dan Abramov <dan.abramov@gmail.com>
Date: Mon, 20 Nov 2017 22:36:54 +0000
Subject: [PATCH] Minor tweaks

---
 content/docs/faq-functions.md | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/content/docs/faq-functions.md b/content/docs/faq-functions.md
index d3204d99..2bc1ddad 100644
--- a/content/docs/faq-functions.md
+++ b/content/docs/faq-functions.md
@@ -24,7 +24,8 @@ There are several ways to make sure functions have access to component attribute
 
 ```jsx
 class Foo extends Component {
-  constructor () {
+  constructor(props) {
+    super(props);
     this.handleClick = this.handleClick.bind(this);
   }
   handleClick() {
@@ -54,7 +55,7 @@ class Foo extends Component {
 
 ```jsx
 class Foo extends Component {
-  handleClick () {
+  handleClick() {
     console.log('Click happened');
   }
   render() {
@@ -65,13 +66,13 @@ class Foo extends Component {
 
 >**Note:**
 >
->Using `Function.prototype.bind` in render creates a new function each time the component renders, which may have performance implications; (see below).
+>Using `Function.prototype.bind` in render creates a new function each time the component renders, which may have performance implications (see below).
 
 #### Arrow Function in Render
 
 ```jsx
 class Foo extends Component {
-  handleClick () {
+  handleClick() {
     console.log('Click happened');
   }
   render() {
@@ -82,7 +83,7 @@ class Foo extends Component {
 
 >**Note:**
 >
->Using an arrow function in render creates a new function each time the component renders, which may have performance implications; (see below).
+>Using an arrow function in render creates a new function each time the component renders, which may have performance implications (see below).
 
 ### Is it OK to use arrow functions in render methods?