From 9ffce755124189a54fb2218523e0354b39f4a174 Mon Sep 17 00:00:00 2001 From: Sam Umbach Date: Sun, 6 Nov 2016 12:03:10 -0500 Subject: [PATCH] Fix minor typo: `effect` => `affect` --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 9f7515d..6614274 100644 --- a/README.md +++ b/README.md @@ -429,7 +429,7 @@ We want to respect the sandbox *inside* each child component, as we don't want t ![CSS Box Model](box-model.png) -My analogies are terrible, but here goes: just like *being inside a country* means being within its physical borders, we establish that a parent can effect styles on its (direct) children only outside the border of the component. That means properties related to positioning and dimensions (e.g. `position`, `margin`, `display`, `width`, `float`, `z-index` etc) are OK, while properties that reach inside the border (e.g. `border` itself, `padding`, `color`, `font` etc) are a no-no. +My analogies are terrible, but here goes: just like *being inside a country* means being within its physical borders, we establish that a parent can affect styles on its (direct) children only outside the border of the component. That means properties related to positioning and dimensions (e.g. `position`, `margin`, `display`, `width`, `float`, `z-index` etc) are OK, while properties that reach inside the border (e.g. `border` itself, `padding`, `color`, `font` etc) are a no-no. As a corollary, this is also very obviously forbidden: