Part 2 layout

docs/01-Concepts.md

@@ -429,9 +429,6 @@ Figures 5 and 6).
 The Frame-Controller-Model (FCM) relationship (or design pattern) is a part of
 Office which programmers will encounter frequently. It appears in the API as
 connections between the XFrame, XController, and XModel interfaces, as shown in
-
-![](images/01-Concepts-11.png)
-
 Figure 11.
 
 
@@ -475,17 +472,13 @@ interfaces, lets me give a more detailed definition of a component. Back in sect
 (and in Figure 4), I said a component was an implemented service. Another way of
 understanding a component is in terms of how much of the FCM relationship it
 supports, which allows the 'component' idea to be divided into three:
-1.  A component that supports both the XModel and XController interfaces is usually
 
+1.  A component that supports both the XModel and XController interfaces is usually
 an Office document.
-
 2.  A component with a controller but no model is typically used to implement library
-
 functionality that doesn't need to load data. Examples include the spell checker,
 and Office tools for creating database forms.
-
 3.  A component with no model or controller (i.e. just an XWindow object) is used
-
 for simple GUI elements, such as Office's help windows.
 
 Of these three types, the component-as-document (number 1) is the most important

docs/03-Examining.md

@@ -93,8 +93,8 @@ class. One way of finding the most current list is to browse main.xcd in
 
 Path settings store directory locations for parts of the Office installation, such as the
 whereabouts of the gallery and spellchecker files. A partial list of predefined paths is
-accessible from within LibreOffice, via the Tools menu: Tools > Options >
-LibreOffice > Paths. But the best source of information is the developer's guide, in the
+accessible from within LibreOffice, via the Tools menu: Tools, Options,
+LibreOffice, Paths. But the best source of information is the developer's guide, in the
 "Path Organization" section of chapter 6, or at
 https://wiki.openoffice.org/wiki/Documentation/DevGuide/OfficeDev/Path_Organizat
 ion, which can be accessed using:
@@ -437,7 +437,7 @@ MRI can be downloaded from
 http://extensions.services.openoffice.org/en/project/mri-uno-object-inspection-tool,
 depositing an OXT file (probably called "MRI-1.3.3.oxt") on your machine.
 
-Installing an extension is done through the Tools > Extension Manager menu item.
+Installing an extension is done through the Tools, Extension Manager menu item.
 
 Click on the "Add" button and select the OXT file. Or you may be able to simply
 double click on the file to start the installation.
@@ -449,7 +449,7 @@ v.1.2.4, at OpenOffice's extension's website
 (http://extensions.services.openoffice.org/en/project/mri-uno-object-inspection-tool)
 did install successfully.
 
-Once installed, MRI can be accessed through Office's GUI via the Tools > Add-ons
+Once installed, MRI can be accessed through Office's GUI via the Tools, Add-ons
 menu item, or programmatically as in my ExamineDoc.java example:
 
 ```java

docs/04-Listening.md

@@ -421,7 +421,7 @@ its close box.
 Another menu-related approach to controlling Office is to programmatically send
 menu shortcut key strokes to the currently active window. For example, a loaded
 Impress document is often displayed with a slide selection pane. This can be closed
-using the menu item View > Slide Pane, which is assigned the shortcut keys ALT-v
+using the menu item View, Slide Pane, which is assigned the shortcut keys ALT-v
 ALT-l.
 
 toggleSlidePane() 'types' these key strokes with the help of Java's Robot class: