aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
author3indblown Leaf <69508345+kraccoon-dev@users.noreply.github.com>2022-03-19 21:24:03 +0900
committerGitHub <noreply@github.com>2022-03-19 21:24:03 +0900
commit59685dd90d01aff63844ed9e6c934a53bc762b6a (patch)
treea88a9d74c41d5edefe40e83949978840c77fd8e6
parent4aa3c3a43e6ed9e09d30f535a65b4938c4082d24 (diff)
downloadtranslated-content-59685dd90d01aff63844ed9e6c934a53bc762b6a.tar.gz
translated-content-59685dd90d01aff63844ed9e6c934a53bc762b6a.tar.bz2
translated-content-59685dd90d01aff63844ed9e6c934a53bc762b6a.zip
[ko] remove unnecessary span tag (#4453)
-rw-r--r--files/ko/web/performance/how_browsers_work/index.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/files/ko/web/performance/how_browsers_work/index.html b/files/ko/web/performance/how_browsers_work/index.html
index 346648524a..818fbea6fa 100644
--- a/files/ko/web/performance/how_browsers_work/index.html
+++ b/files/ko/web/performance/how_browsers_work/index.html
@@ -128,7 +128,7 @@ original_slug: Web/Performance/브라우저는_어떻게_동작하는가
<h3 id="Building_the_CSSOM">Building the CSSOM</h3>
-<p>The second step in the critical rendering path is processing CSS and building the CSSOM tree. The CSS object model is similar to the DOM. <span style="color: #212121; display: inline !important; float: none; font-family: Roboto,sans-serif; font-size: 16px; font-style: normal; font-weight: 400; letter-spacing: normal; text-align: left; text-decoration-style: initial; text-indent: 0px; text-transform: none; white-space: normal;">The DOM and CSSOM are both trees. They are independent data structures</span>. The browser converts the CSS rules into a map of styles it can understand and work with. The browser goes through each rule set in the CSS, creating a tree of nodes with parent, child, and sibling relationships based on the CSS selectors.</p>
+<p>The second step in the critical rendering path is processing CSS and building the CSSOM tree. The CSS object model is similar to the DOM. The DOM and CSSOM are both trees. They are independent data structures. The browser converts the CSS rules into a map of styles it can understand and work with. The browser goes through each rule set in the CSS, creating a tree of nodes with parent, child, and sibling relationships based on the CSS selectors.</p>
<p>As with HTML, the browser needs to convert the received CSS rules into something it can work with. Hence, it repeats the HTML-to-object process, but for the CSS.</p>