[royale-docs] branch master updated: Update migrate-from-flex.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 4108b07  Update migrate-from-flex.md
4108b07 is described below

commit 4108b07aacbed21de95c8362e8673cabd33da47f
Author: Andrew Wetmore <an...@cottage14.com>
AuthorDate: Thu Jan 9 14:00:33 2020 -0400

    Update migrate-from-flex.md
    
    Added link to emulation page
---
 migrate-an-existing-app/migrate-from-flex.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/migrate-an-existing-app/migrate-from-flex.md b/migrate-an-existing-app/migrate-from-flex.md
index 79b6c05..543f4da 100644
--- a/migrate-an-existing-app/migrate-from-flex.md
+++ b/migrate-an-existing-app/migrate-from-flex.md
@@ -39,7 +39,7 @@ There are areas in your code base that will have to change. One is anywhere that
 
 To determine where you may have used Flash APIs, look for "import flash" in your code. If you comment out all the "import flash" lines and re-compile, the compiler will show you every line that uses a Flash API.
 
-Royale is creating a set of **emulation** components that will eventually deliver most, if not all, of the Flex APIs. These components do not promise 100% backward compatibility. Nor do they promise the same class hierarchy as Flex. They just try to approximate what Flex did.
+Royale is creating a set of [emulation](/migrate-an-existing-app/emulation) components that will eventually deliver most, if not all, of the Flex APIs. These components do not promise 100% backward compatibility. Nor do they promise the same class hierarchy as Flex. They just try to approximate what Flex did.
 
 Some popular Flash APIs have been added to the Royale emulation of UIComponent, so review the documentation for UIComponent to see if it has a replacement for a Flash API your old app uses. If a replacement doesn't exist, it either hasn't been implemented yet in the emulation components or we have a good reason why it shouldn't be. Ask on the users@royale.apache.org mailing list if you want to know more about an emulation for a particular API.