Fixes more broken links in migrated wiki pages

docs/Execution_Environments.md

@@ -212,9 +212,9 @@ specification. These are summarized in the table below.
 
 ## Installing Execution Environment Descriptions
 
-Latest Execution Environment Descriptions can be installed from the
-current release update site:  
-[<https://download.eclipse.org/eclipse/updates/4.3>](https://download.eclipse.org/eclipse/updates/4.3)  
+Latest Execution Environment Descriptions can be installed from the release update site, for example:
+
+[Eclipse 4.3 update site](https://download.eclipse.org/eclipse/updates/4.3)  
 When using the 4.3 Kepler update site the environments are contained in
 a single installable unit labelled "API Tools Execution Environment
 Descriptions" inside a category of the same name. Previous releases

docs/FAQ.md

@@ -152,7 +152,7 @@ Earlier versions of PDE did not automatically add a "." when a Bundle-Classpath
 
 ### Why am I getting a "package uses conflict"?
 
-["Package uses"](http://blog.springsource.com/2008/10/20/understanding-the-osgi-uses-directive/) are akin to a bundle's require-bundles: they specify a package's dependent packages. [Package-uses conflicts](http://njbartlett.name/2011/02/09/uses-constraints.html) are fortunately somewhat rare, but are obscure and difficult-to-diagnose problems. Basically they occur when a bundle's imports causes two different versions of a package to be available within the same bundle — there is no way for the framework to decide which package to allow. The articles linked to earlier in this paragraph provide more detail.
+["Package uses"](http://blog.springsource.com/2008/10/20/understanding-the-osgi-uses-directive/) are akin to a bundle's require-bundles: they specify a package's dependent packages.  Package uses conflicts  are fortunately somewhat rare, but are obscure and difficult-to-diagnose problems. Basically they occur when a bundle's imports causes two different versions of a package to be available within the same bundle — there is no way for the framework to decide which package to allow. The articles linked to earlier in this paragraph provide more detail.
 
 Package uses conflicts often occur with system-level packages from the JVM's execution environment (e.g., javax.transaction) are made available, either via system bundle extensions or the org.osgi.framework.system.packages and org.osgi.framework.system.packages.extra properties (and possibly the Equinox Launcher's [compatibility boot-delegation](/Equinox_Boot_Delegation "Equinox Boot Delegation") too). For example, many modern JREs now include javax.transaction, javax.annotation, javax.inject, and javax.vecmath, which many apps previously brought in through other bundles. When these packages are exposed through the system bundle, any bundle that re-exports the system bundle (notably org.eclipse.core.runtime) will also expose those classes. Conflicts arise when also including a bundle using a "Dynamic-ImportPackage" as the import set has to be verified against the packages available.
 

docs/User_Guide.md

@@ -668,7 +668,8 @@ Menus and Actions
 
 ### API Tooling Setup
 
-Select the **API Tooling Setup** command \[ ![Pde category menu.gif](https://raw.githubusercontent.com/eclipse-pde/eclipse.pde/master/docs/images/Pde_category_menu.gif)\] to start the API Setup wizard.
+
+Select the **API Tooling Setup** command ![Pde category menu.gif](https://raw.githubusercontent.com/eclipse.pde/master/docs/images/Pde_category_menu.gif) to start the API Setup wizard.
 
 ### API Baseline