Merge "Add libGL fix for Ubuntu 10.10"
diff --git a/src/source/build-numbers.md b/src/source/build-numbers.md
index 09d2c5c..cbdf721 100644
--- a/src/source/build-numbers.md
+++ b/src/source/build-numbers.md
@@ -89,7 +89,9 @@
 FRG22D | android-2.2_r1.3
 FRG83  | android-2.2.1_r1   | Nexus One
 FRG83D | android-2.2.1_r2   | Nexus One
-FRG83G | android-2.2.2_r1   | latest Froyo version, Nexus One
+FRG83G | android-2.2.2_r1   | Nexus One
+FRK76  | android-2.2.3_r1
+FRK76C | android-2.2.3_r2   | latest Froyo version
 GRH55  | android-2.3_r1     | earliest Gingerbread version, Nexus S
 GRH78  | android-2.3.1_r1   | Nexus S
 GRH78C | android-2.3.2_r1   | Nexus S
diff --git a/src/source/code-lines.md b/src/source/code-lines.md
index 1d6d421..8b268f2 100644
--- a/src/source/code-lines.md
+++ b/src/source/code-lines.md
@@ -28,7 +28,7 @@
 will become a new branch in git, and sometimes not, based on the needs of the
 moment.
 
-<img src="/images/code-lines.png"/>
+<img src="/images/code-lines.png" alt="code-line diagram"/>
 
 ## Notes and Explanations ##
 
diff --git a/src/source/life-of-a-patch.md b/src/source/life-of-a-patch.md
index 7799424..f0fbc40 100644
--- a/src/source/life-of-a-patch.md
+++ b/src/source/life-of-a-patch.md
@@ -24,4 +24,4 @@
 For full instructions on how to get set up to use gerrit and git, please
 see the [Submitting Patches](submit-patches.html) page.
 
-<img src="/images/workflow-0.png"/>
+<img src="/images/workflow-0.png" alt="workflow diagram"/>
diff --git a/src/source/version-control.md b/src/source/version-control.md
index 623e30f..110048a 100644
--- a/src/source/version-control.md
+++ b/src/source/version-control.md
@@ -27,7 +27,7 @@
 ## Basic Workflow ##
 
 <div style="float:right">
-  <img src="/images/submit-patches-0.png">
+  <img src="/images/submit-patches-0.png" alt="basic workflow diagram">
 </div>
 
 The basic pattern of interacting with the repositories is as follows:
@@ -60,7 +60,7 @@
 ## Creating topic branches ##
 
 Start a topic branch in your local work environment whenever you begin a change, for example when you begin work on a bug or new feature. A topic branch is not a copy of the original files; it is a pointer to a particular commit. This makes creating local branches and switching among them a light-weight operation. By using branches, you can isolate one aspect of your work from the others. For an interesting article about using topic branches, see [Separating topic branches](http://www.kernel.org/pub/software/scm/git/docs/howto/separating-topic-branches.txt).
-<img src="/images/external-link.png">
+<img src="/images/external-link.png" alt="">
 
 To start a topic branch using Repo: 
 
@@ -173,6 +173,6 @@
 
 # Git and Repo cheatsheet #
 
-<img src="/images/git-repo-1.png">
+<img src="/images/git-repo-1.png" alt="list of basic git and repo commands">