docs/extensions/troubleshooting.md

 # Troubleshooting
 
-If you are struggling, the best thing to do is reach out to the [CiviCRM community](/basics/community.md).
+If you are struggling, the best thing to do is reach out to the [CiviCRM community](../basics/community.md).
 
 If you cannot find the answer in this guide or by searching in the [CiviCRM StackExchange site](http://civicrm.stackexchange.com/) then please [ask](http://civicrm.stackexchange.com/questions/ask). Asking questions on StackExchange not only helps you but may well help others who follow you.
 
@@ -22,7 +22,7 @@ A: You might have missed the step about setting 'civicrm\_api3\_conf\_path' ([ht
 
 Q: I've tried to generate a page/report/search/upgrader/etc with civix but it's not working.
 
-A: For all of the various types, you must first run [generate:module](http://generatemodule), and then \`cd\` into the folder (e.g. com.example.myextension) before running one of the other \`generate:\` commands.
+A: For all of the various types, you must first run [generate:module](civix.md#generate-module), and then \`cd\` into the folder (e.g. com.example.myextension) before running one of the other \`generate:\` commands.
 
 ## Out-of-date templates
 

docs/financial/overview.md

-!!! abstract
-    This area of CiviCRM code and documentation is a work-in-progress. Not all features
-    will be documented and the core code underlying this area may change from version
-    to version.
-
 The financial subsystem in civicrm encompasses:
 
 - contributions

docs/financial/paymentAPI.md

-!!! abstract
-    This area of CiviCRM code and documentation is a work-in-progress. Not all features
-    will be documented and the core code underlying this area may change from version
-    to version.
-
 ## Payment API
 
 Historically, one recorded a payment against a contribution by changing its payment status, for example from Pending to Completed. 

docs/framework/ajax.md

@@ -2,7 +2,8 @@
 
 ## Background
 
-The CiviCRM page request lifecycle has always been closely coupled with traditional web browsing. In recent versions we have been using more ajax, but adapting our page/form controllers to that context has been somewhat cumbersome. In 4.5 several new layers have been added to facilitate using traditional html forms/pages with ajax.
+This documents CiviCRM's jQuery-based AJAX framework. These functions are old (circa CiviCRM 4.5) but still useful as they allow mixing different architectures on the same page
+(e.g. an Angular-based Afform can load a QuickForm-based page in an AJAX popup). This allows incrementatal refactoring of various CiviCRM UIs without requiring everything to be rewritten at once.
 
 ## High Level Sugar
 
@@ -13,7 +14,9 @@ Handler for a jQuery event e.g. `$('a').click(CRM.popup);`
 !!! note "Automatic via CSS Class"
     Often you do not need to write javascript at all to use this function. CiviCRM will automatically call it when any `<a>` with class `crm-popup` is clicked.
 
-    This function invokes the entire ajax stack (`jQuery dialog`, `crmSnippet`, `jquery.forms`, and `jquery.validate`) by calling `CRM.loadForm` and `CRM.refreshParent` when appropriate.
+This function invokes the entire ajax stack (`jQuery dialog`, `crmSnippet`, `jquery.forms`, and `jquery.validate`) by calling `CRM.loadForm` and `CRM.refreshParent` when appropriate.
+
+You can also add class `small-popup` (400px width), `medium-popup` (50% width or more) or leave it as default, which will vary from 65% width or more depending on window width. 
 
 #### Options
 
@@ -206,6 +209,6 @@ CRM.$(function($) {
 ## Additional Notes
 
 - Variables added via `CRM_Core_Resources` will be loaded as part of a snippet - new variables will be appended to the CRM object, and existing variables with the same name will be overwritten.
-- Scripts added via `CRM_Core_Resources` will be loaded as part of a snippet. This may not always be desirable, e.g. if the same snippet is refreshed multiple times it will reload all scripts every time. To avoid a script loading into a snippet one could specify the `html-header` region for the script. See [Resource Reference](/framework/resources.md).
+- Scripts added via `CRM_Core_Resources` will be loaded as part of a snippet. This may not always be desirable, e.g. if the same snippet is refreshed multiple times it will reload all scripts every time. To avoid a script loading into a snippet one could specify the `html-header` region for the script. See [Resource Reference](resources.md).
 - Javascript header scripts, notably the wysiwyg editor library, are not loaded automatically, which causes many forms to not work without manually loading the necessary scripts prior to the ajax call.
 - If the page/form directly issues a redirect it will prevent ajax from working. Best practice is to not use `CRM_Utils_System::redirect()` but instead use `CRM_Core_Session::pushUserContext()` and allow the core controller to take care of the rest.