[royale-docs] branch master updated: edit

[ha...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

harbs pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/royale-docs.git


The following commit(s) were added to refs/heads/master by this push:
     new ba0e8bd  edit
ba0e8bd is described below

commit ba0e8bda35e0a08caab65efa60ed2526edf1e16e
Author: Harbs <ha...@in-tools.com>
AuthorDate: Thu Dec 30 12:22:44 2021 +0200

    edit
---
 features/modules.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/features/modules.md b/features/modules.md
index 8a405b7..c6aa5db 100644
--- a/features/modules.md
+++ b/features/modules.md
@@ -49,7 +49,7 @@ Proper use of modules can help maintain _"separation of concerns"_ which helps k
 ## Why not modules? {#why-not-modules}
 In Flash, modules was very important. That's because application size and compilation time grew very rapidly. Flash applications were slow to load and modules were a good tool to help with that. The aggressive use of PAYG in Royale along with browser features for loading Javascript made Royale applications much smaller and load times generally nearly instant. In many (most?) use cases of modules for Flex applications in Flash, Royale renders them unnecessary.
 
-Using modules can make development more difficult and in some cases cause your application to actually load _*slower*_. Before using modules, consider the following points:
+Using modules can make development more difficult and in some cases cause your application to actually load _**slower**_. Before using modules, consider the following points:
 
 * You will see huge drops in compilation speed when switching from Flash to HTML Royale for the same application.
 * The application size dropped drastically as well, and the whole application will often become about the size of a single module.