update url of example pom.xml files, minor pom.xml updates, mention t…

…hat test still works on Embedded GlassFish

guides/getting_started.textile

@@ -111,7 +111,6 @@ bc(prettify).. <?xml version="1.0" encoding="UTF-8"?>
     <build>
         <plugins>
             <plugin>
-                <groupId>org.apache.maven.plugins</groupId>
                 <artifactId>maven-compiler-plugin</artifactId>
                 <version>2.3.2</version>
                 <configuration>
@@ -387,13 +386,12 @@ div(filename). pom.xml
 
 bc(prettify).. <!-- clip -->
 <plugin>
-    <groupId>org.apache.maven.plugins</groupId>
     <artifactId>maven-surefire-plugin</artifactId>
     <version>2.12</version>
 </plugin>
 <!-- clip -->
 
-p. If you're having trouble with the pom.xml up to this point, you can download the file from "this gist":https://gist.github.com/1263892.
+p. If you're having trouble with the pom.xml up to this point, you can download the file "pom-no-container-profiles.xml":https://raw.github.com/arquillian/arquillian-examples/master/arquillian-tutorial/pom-no-container-profiles.xml from the "example project":https://github.com/arquillian/arquillian-examples/tree/master/arquillian-tutorial and rename it to pom.xml.
 
 *You're all set to write your first Arquillian test!*
 
@@ -871,7 +869,7 @@ p(info). %By default, JBoss AS 7 deploys test archives to the server using the J
 
 p. You now have the choice of running the tests in one of three containers.
 
-p. If you're having trouble with the pom.xml up to this point, you can download the file from "this gist":https://gist.github.com/1263934.
+p. If you're having trouble with the pom.xml up to this point, you can download the file "pom.xml":https://raw.github.com/arquillian/arquillian-examples/master/arquillian-tutorial/pom.xml from the "example project":https://github.com/arquillian/arquillian-examples/tree/master/arquillian-tutorial.
 
 h3. Test Across Containers
 
@@ -945,8 +943,7 @@ To run the test on a standalone instance of JBoss AS, you first need to set it u
 
 Follow these steps to setup JBoss AS 7 outside the project:
 
-# "Download JBoss AS 7":as7_download
-(be sure the version you select matches the version you've defined in your @pom.xml@ for @<artifactId>jboss-as-arquillian-container-managed</artifactId>@)
+# "Download JBoss AS 7":as7_download (make sure the version you download matches the version of the @jboss-as-arquillian-container-managed@ dependency in your @pom.xml@)
 # Extract the archive
 # (optional) Set the @JBOSS_HOME@ environment variable to the path of the extracted directory
 

guides/getting_started_rinse_and_repeat.textile

@@ -407,7 +407,7 @@ We are done with JBoss AS for the moment, so use the Servers view to stop the se
 
 h4. Run the Test on GlassFish
 
-To run the test on GlassFish, begin by starting the GlassFish container. Open the Servers view, select GlassFish 3.1.2, then click the green play button. Wait for it to start.
+To run the test on the standalone GlassFish server, begin by starting the server. Open the Servers view, select GlassFish 3.1.2, then click the green play button. Wait for it to start.
 
 Once that's up and running, activate the @arquillian-glassfish-remote@ Maven profile using either the Maven properties tab or the JBoss Tools Maven profile selector. Remember to deactivate the @arquillian-jbossas-remote@ profile. The profile editor below shows the correct selection.
 
@@ -430,6 +430,10 @@ Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.549 sec
 
 *Congratulations!* You've earned another *(greenbar)green bar*.
 
+You should still be able to run the test on Embedded GlassFish using the profile you setup in the previous guide. Give it a try. You should also be able to debug the test easily.
+
+Of course, debugging the test in an embedded container is easy since it runs in the same process as the test launcher. But what about a remote container?
+
 h3. Debug the Arquillian Test
 
 Debugging a test in a remote container? That seems hard. Surprise! It's not at all. You only have to modifiy one of the step above and add one additional step: