From 4168f453784ac45226560bd72ee65495d1b5e6ca Mon Sep 17 00:00:00 2001
From: Krekotun <Krekotun@users.noreply.github.com>
Date: Sat, 11 Apr 2015 13:10:23 +0300
Subject: [PATCH] Update 08-modular-development.md

remove comma
---
 chapters/08-modular-development.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/chapters/08-modular-development.md b/chapters/08-modular-development.md
index 45f21df7..286b3876 100644
--- a/chapters/08-modular-development.md
+++ b/chapters/08-modular-development.md
@@ -25,7 +25,7 @@ You might be thinking that there is little benefit to RequireJS. After all, you
 Every time the browser loads in a file you've referenced in a `<script>` tag, it makes an HTTP request to load the file's contents. It has to make a new HTTP request for each file you want to load, which causes problems.
 
 - Browsers are limited in how many parallel requests they can make, so often it's slow to load multiple files, as it can only do a certain number at a time. This number depends on the user's settings and browser, but is usually around 4-8. When working on Backbone applications it's good to split your app into multiple JS files, so it's easy to hit that limit quickly. This can be negated by minifying your code into one file as part of a build process, but does not help with the next point.
-- Scripts are loaded synchronously. This means that the browser cannot continue page rendering while the script is loading, .
+- Scripts are loaded synchronously. This means that the browser cannot continue page rendering while the script is loading.
 
 What tools like RequireJS do is load scripts asynchronously. This means we have to adjust our code slightly, you can't just swap out `<script>` elements for a small piece of RequireJS code, but the benefits are very worthwhile: