From ce954be65ca8205869ca443d266b456826faceb6 Mon Sep 17 00:00:00 2001
From: Suzanne Millstein <smillst@cs.washington.edu>
Date: Thu, 1 Oct 2020 14:15:47 -0700
Subject: [PATCH] Fix more links.

---
 docs/manual/accumulation-checker.tex   | 2 +-
 docs/manual/called-methods-checker.tex | 2 +-
 docs/manual/creating-a-checker.tex     | 4 ++--
 docs/manual/signedness-checker.tex     | 2 +-
 4 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/docs/manual/accumulation-checker.tex b/docs/manual/accumulation-checker.tex
index ae8ab0aebd7..c2d3c161854 100644
--- a/docs/manual/accumulation-checker.tex
+++ b/docs/manual/accumulation-checker.tex
@@ -17,7 +17,7 @@
 The Called Methods Checker (\chapterpageref{called-methods-checker})
 is an accumulation analysis.
 The
-\href{https://github.com/typetools/checker-framework/blob/master/framework/src/test/java/testaccumulation/TestAccumulationChecker.java}{Test Accumulation Checker}
+\href{https://github.com/typetools/checker-framework/blob/master/framework/src/test/java/org/checkerframework/framework/testchecker/testaccumulation/TestAccumulationChecker.java}{Test Accumulation Checker}
 is a simplified version of the Called Methods Checker that you can also use as a model.
 
 Accumulation analysis is a special case of typestate analysis in which
diff --git a/docs/manual/called-methods-checker.tex b/docs/manual/called-methods-checker.tex
index f57f48779bc..a2016912e8c 100644
--- a/docs/manual/called-methods-checker.tex
+++ b/docs/manual/called-methods-checker.tex
@@ -233,7 +233,7 @@
 specify some trusted source for the image by calling the \<withOwners> or
 \<withImageIds> methods on the request prior to sending it to AWS\@. Using
 a stub file for the \<describeImages> API
-(\href{https://github.com/typetools/checker-framework/blob/master/checker/src/main/java/org/checkerframework/calledmethods/DescribeImages.astub}{DescribeImages.astub}),
+(\href{https://github.com/typetools/checker-framework/blob/master/checker/src/main/java/org/checkerframework/checker/calledmethods/DescribeImages.astub}{DescribeImages.astub}),
 the Called Methods Checker can prove that a client is not vulnerable to
 such an attack.
 
diff --git a/docs/manual/creating-a-checker.tex b/docs/manual/creating-a-checker.tex
index c440dabcf91..698055dc25e 100644
--- a/docs/manual/creating-a-checker.tex
+++ b/docs/manual/creating-a-checker.tex
@@ -1193,7 +1193,7 @@
 \begin{enumerate}
 \item
   Define a subclass of
-  \refclass{org/checkerframework/framework/type/treeannotator}{TreeAnnotator},
+  \refclass{framework/type/treeannotator}{TreeAnnotator},
   typically as a private inner class of your \<AnnotatedTypeFactory>.
   There is a method of \<TreeAnnotator> for every AST node, and the visitor
   has access to both the tree (the AST node) and its type.  In your
@@ -1215,7 +1215,7 @@
 
 \item
   Define a subclass of a
-  \refclass{org/checkerframework/framework/type/typeannotator}{TypeAnnotator},
+  \refclass{framework/type/typeannotator}{TypeAnnotator},
   typically as a private inner class of your \<AnnotatedTypeFactory>.
   There is a method of \<TypeAnnotator> for every kind of type, and the
   visitor has access to only the type.  In your subclass of
diff --git a/docs/manual/signedness-checker.tex b/docs/manual/signedness-checker.tex
index a0ce6751a6b..a717c719304 100644
--- a/docs/manual/signedness-checker.tex
+++ b/docs/manual/signedness-checker.tex
@@ -69,7 +69,7 @@
     write \refqualclass{checker/signedness/qual}{Signed} or
     \refqualclass{checker/signedness/qual}{Unsigned} instead.
 
-\item[\refqualclass{checker/signedness/qual}{SignedPositiveFromUnsigend}]
+\item[\refqualclass{checker/signedness/qual}{SignedPositiveFromUnsigned}]
     indicates that a value is in the positive signed range, as with
     \refqualclass{checker/signedness/qual}{SignedPositive}.  Furthermore,
     the value was derived from values that can be interpreted as