[royale-docs] branch master updated: Update application-structure.md

[an...@apache.org]

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

andreww 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 e91babe  Update application-structure.md
e91babe is described below

commit e91babe598627afd5065ac442cc0ad3c5182f483
Author: Andrew Wetmore <an...@cottage14.com>
AuthorDate: Sun Dec 8 07:59:16 2019 -0400

    Update application-structure.md
    
    Minor text edits
---
 create-an-application/application-structure.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/create-an-application/application-structure.md b/create-an-application/application-structure.md
index 68105a6..5ef2b8d 100644
--- a/create-an-application/application-structure.md
+++ b/create-an-application/application-structure.md
@@ -24,11 +24,11 @@ permalink: /create-an-application/application-structure
 
 All about the organization of your project files and folders
 
-Royale applications are usually comprised of many files. If you are in rapid-prototyping or proof-of-concept "get something small running quickly" mode, you can cram everything into one file. But breaking things into multiple pieces often helps you organize or create "separation of concerns", and as your project and team grows, you and your teammates can work on individual pieces independently without stepping on each other's work. Finally, coherent pieces that perform some standard func [...]
+Royale applications usually include many files. If you are in rapid-prototyping or proof-of-concept "get something small running quickly" mode, you can cram everything into one file. But breaking things into multiple pieces often helps you organize your code and create "separation of concerns"; and as your project and team grows, you and your teammates can work on individual pieces independently without stepping on each other's work. Finally, you can more easily re-use coherent pieces th [...]
 
-There are multiple popular ways of dividing an Application into coherent and reusable pieces: Model-View (MV), Model-View-Controller (MVC), and other alphabet soup like MVP, MVVM, HMVC and more. This documentation will not address these patterns in detail. You can read more about them on the internet.
+There are multiple popular ways of dividing an application into coherent and reusable pieces: Model-View (MV), Model-View-Controller (MVC), and other alphabet soup like MVP, MVVM, HMVC and more. This documentation will not address these patterns in detail. You can read more about them on the internet.
 
-> Whatever you decide for how many files you will have, another thing to keep in mind is that Royale can produce different kinds of output, like SWFs for Adobe FlashPlayer or Adobe AIR as well as HTML/JS/CSS for browsers and Apache Cordova applications.  So, the recommended practice is to create a folder for your project files and a set of subfolders within it. The Royale compiler detects certain common folder patterns and automatically chooses where to put output folders, although you c [...]
+> Whatever you decide for how many files you will have, another thing to keep in mind is that Royale can produce different kinds of output, like SWFs for Adobe FlashPlayer or Adobe AIR and HTML/JS/CSS files for browsers and Apache Cordova applications. So, the recommended practice is to create a folder for your project files and a set of subfolders within it. The Royale compiler detects certain common folder patterns and automatically chooses where to put output folders, although you can [...]
 
 If you are using an [IDE](get-started/development-tools) that supports Royale, it will create the standard folder structure for you when you create a Royale project. If you are working outside of an IDE, and perhaps using command-line instructions to compile your code, here is how to structure your project.
 
@@ -36,9 +36,9 @@ Let's say you are creating a project called `MyFirstRoyaleApp`. Create a `MyFirs
 
 If you use [Apache Maven](https://maven.apache.org){:target='_blank'} to build your app, you can use one of the [Maven archetypes](get-started/development-tools.html#apache-maven), which put the main application source code 3 levels deep in a `src/main/royale` folder structure. Other kinds of files then go in `src/main/resource`, `src/main/config` and so on. Maven instructs the compiler to put the output in a `target/javascript/bin` folder.
 
-Most Royale applications use an [MXML](features/mxml) file as the main application file. Other files are written in MXML or [ActionScript](features/as3) depending on whether you are assembling pieces or writing custom logic. You can write a Royale Application without using MXML at all, but you'll end up writing more code.
+Most Royale applications use an [MXML](features/mxml) file as the main application file. Write other files in MXML or [ActionScript](features/as3) depending on whether you are assembling pieces or writing custom logic. You can write a Royale application without using MXML at all, but you'll end up writing more code.
 
-So, if you decide to use MXML as your main application file, then your folder structure might look like this:
+So, if you decide to use MXML as your main application file, your folder structure might look like this:
 
 ```
 -MyFirstRoyaleApp