Fix some AsciiDoc links (WIP)

Signed-off-by: Alexander Kriegisch <Alexander@Kriegisch.name>

3 files changed, 9 insertions, 8 deletions

diff --git a/docs/progGuideDB/gettingstarted.adoc b/docs/progGuideDB/gettingstarted.adoc
index 0930d2e44..0dbb85056 100644
--- a/docs/progGuideDB/gettingstarted.adoc
+++ b/docs/progGuideDB/gettingstarted.adoc
@@ -23,7 +23,8 @@ examples illustrate the kinds of aspects programmers may want to
 implement using AspectJ and the benefits associated with doing so.
 Readers who would like to understand the examples in more detail, or who
 want to learn how to program examples like these, can find more complete
-examples and supporting material linked from the https://www.eclipse.org/aspectj/:[AspectJ web site].
+examples and supporting material linked from the
+https://www.eclipse.org/aspectj/[AspectJ web site].
 
 A significant risk in adopting any new technology is going too far too
 fast. Concern about this risk causes many organizations to be
@@ -38,7 +39,7 @@ testing and performance tuning of applications. And, in the section
 following, xref:#starting-production[Production Aspects], we present
 aspects that implement crosscutting functionality common in Java
 applications. We will defer discussing a third category of aspects,
-reusable aspects, until xref:#language[???].
+reusable aspects, until xref:language.adoc[The AspectJ Language].
 
 These categories are informal, and this ordering is not the only way to
 adopt AspectJ. Some developers may want to use a production aspect right
@@ -945,8 +946,8 @@ are also highly modular, making it possible to develop plug-and-play
 implementations of crosscutting functionality.
 
 AspectJ provides more functionality than was covered by this short
-introduction. The next chapter, xref:#language[???], covers in detail
+introduction. The next chapter, xref:language.adoc[The AspectJ Language], covers in detail
 more of the features of the AspectJ language. The following chapter,
-xref:#examples[???], then presents some carefully chosen examples that
+xref:examples.adoc[Examples], then presents some carefully chosen examples that
 show you how AspectJ might be used. We recommend that you read the next
 two chapters carefully before deciding to adopt AspectJ into a project.
diff --git a/docs/progGuideDB/language.adoc b/docs/progGuideDB/language.adoc
index 44f17dcb5..f48cc4290 100644
--- a/docs/progGuideDB/language.adoc
+++ b/docs/progGuideDB/language.adoc
@@ -4,7 +4,7 @@
 [[language-intro]]
 === Introduction
 
-The previous chapter, xref:#starting[???], was a brief overview of the
+The previous chapter, xref:gettingstarted.adoc[Getting Started with AspectJ], was a brief overview of the
 AspectJ language. You should read this chapter to understand AspectJ's
 syntax and semantics. It covers the same material as the previous
 chapter, but more completely and in much more detail.
@@ -187,7 +187,7 @@ In object-oriented programs, there are several kinds of "things that
 happen" that are determined by the language. We call these the join
 points of Java. Join points consist of things like method calls, method
 executions, object instantiations, constructor executions, field
-references and handler executions. (See the xref:#quick[???] for a
+references and handler executions. (See the xref:quickreference.adoc#quick[AspectJ Quick Reference] for a
 complete listing.)
 
 Pointcuts pick out these join points. For example, the pointcut
@@ -415,7 +415,7 @@ aspect A  {
 The `!within(A)` pointcut above is required to avoid the `printPC`
 pointcut applying to the `System.out.println` call in the advice body.
 If this was not present a recursive call would result as the pointcut
-would apply to its own advice. (See xref:#pitfalls-infiniteLoops[???]
+would apply to its own advice. (See xref:pitfalls.adoc#pitfalls-infiniteLoops[Infinite loops]
 for more details.)
 
 ==== Pointcut Parameters
diff --git a/docs/progGuideDB/semantics.adoc b/docs/progGuideDB/semantics.adoc
index 5a3e7fb00..1943aa609 100644
--- a/docs/progGuideDB/semantics.adoc
+++ b/docs/progGuideDB/semantics.adoc
@@ -2487,7 +2487,7 @@ a join point picked out by <Pointcut> where there is no associated
 aspect of type A.
 
 Both `perthis` and `pertarget` aspects may be affected by code the
-AspectJ compiler controls, as discussed in the xref:#implementation[???]
+AspectJ compiler controls, as discussed in the xref:implementation.adoc#implementation[Implementation Notes]
 appendix.
 
 ===== Per-control-flow aspects