Revert "Manual fixes for a number of rumdl warnings"

This reverts commit d58c30f.

Author: Fryguy

README.md

@@ -13,6 +13,7 @@
   * [Openshift](providers/openshift.md)
   * [Openstack Infra](providers/openstack_infra_provider.md)
   * [Interactive debugging with Pry-Remote](developer_setup/debugging.md)
+* [Running in minimal mode](developer_setup/minimal_mode.md)
 * [Running the test suites](developer_setup/running_test_suites.md)
 * [Running Cypress tests](ui/cypress.md)
 * [Setting up Kubernetes for use with ManageIQ](providers/kubernetes.md)
@@ -24,12 +25,14 @@
 * [Coding Style and Standards](coding_style_and_standards.md)
 * [Contributing to the API](https://github.com/ManageIQ/manageiq-api/blob/master/CONTRIBUTING.md)
 * [External Authentication (httpd)](external_auth.md)
+* [GIT Helpers](git_utils/README.md)
 * [Issue and PR Triage Process](triage_process.md)
 * [Internationalization Guidelines](i18n.md)
 * [Merger Guidelines](mergers_guidelines.md)
 * [Project Roadmap](https://github.com/orgs/ManageIQ/projects/13)
 * [Repository Labels and Colors](labels.md)
 * [Reviewer Guidelines](reviewers_guidelines.md)
+* [Sprint Boundaries](sprint_boundaries.md)
 * [UI Patterns](ui/patterns.md)
 * [UI Plugins](ui/plugins.md)
 * [Updating this Documentation](writing_guides.md)

architecture/enterprise.md

@@ -73,7 +73,7 @@ collisions when database synchronization combines the various regions into the
 
 ### Visual example
 
-```text
+<pre>
  Region
 +--------------------------------------------------------------+
 |                                                              |
@@ -92,4 +92,4 @@ collisions when database synchronization combines the various regions into the
 |  +--------------------------+  +--------------------------+  |
 |                                                              |
 +--------------------------------------------------------------+
-```
+</pre>

architecture/logging.md

@@ -3,7 +3,7 @@
 ManageIQ uses the standard Ruby [Logger](https://ruby-doc.org/stdlib-2.6.6/libdoc/logger/rdoc/Logger.html)
 interface, with a custom formatter that is mostly just minor changes from the
 default formatter. Additionally, we use a logger abstraction library, called
-[manageiq-loggers](https://github.com/ManageIQ/manageiq-loggers) in order to support
+[manageiq-loggers](github.com/ManageIQ/manageiq-loggers) in order to support
 multiple log targets and formats.
 
 An example log message looks like:

architecture/source_code_layout.md

@@ -17,7 +17,7 @@ ManageIQ is a Rails application with the following standard layout
 | Rakefile    | This file locates and loads tasks that can be run from the command line. The task definitions are defined throughout the components of Rails. Rather than changing Rakefile, you should add your own tasks by adding files to the lib/tasks directory of your application. |
 | README.md   | Overview of the ManageIQ project. |
 | [spec/](#spec)       | Tests using RSpec. |
-| tools       | Special purpose Ruby scripts that should not be executed without full understanding of what they do. |
+| [tools/](#tools) | Special purpose Ruby scripts that should not be executed without full understanding of what they do. |
 | tmp/        | Temporary files (like cache, pid, and session files). |
 | vendor/     | A place for all third-party code. |
 

proposals/automate_model_redesign.md

@@ -18,10 +18,10 @@ The Automate Model has grown to be a very large and central piece of ManageIQ. T
 ## Proposal
 
 * Provide clear separation between core automate model and user space where built-in automate methods are viewable but read-only. Allow end users to duplicate built-in automate model objects and utilize them. Any modifications that bridge core automate and user space must survive model upgrade.
-* Reorganize classes and folders logically. [See proposal below](#proposed-namespaceclass-restructure).
+* Reorganize classes and folders logically. [See proposal below](Automate-Model-Redesign#proposed-namespaceclass-restructure).
 * Reorganize integration namespace to be a central place for all customer integration
 * Enable text-based editing through familiar directory hierarchy and files (see below)
-  * schema: YAML syntax. [example](#proposed-example-schemayaml)
+  * schema: YAML syntax. [example](Automate-Model-Redesign#proposed-example-schemayaml)
   * methods: ruby files
 * Provide command-line simulation tool for complete CLI-based development/debugging workflow. This will also provide a tool for automated testing.
 * Automate hierarchy should have a view of the "community" models which may be selected and imported into ManageIQ. See planned [Github space](https://github.com/RedHatIntegrate/CloudForms-Management-Engine) for community models.

providers/kubernetes.md

@@ -31,33 +31,33 @@ Based on instructions for deploying Kubernetes manually from here: <https://kube
 
 Ensure the following conditions are met:
 
-1. In `/etc/kubernetes/kubelet`, ensure `KUBELET_ARGS` contains `--allow-privileged`
-2. On the master node, generate a default serviceaccount key with `openssl genrsa -out /tmp/serviceaccount.key 2048`
-3. In `/etc/kubernetes/apiserver`, ensure `KUBE_API_ARGS` contains `--service_account_key_file=/tmp/serviceaccount.key` (or the correct path to your default serviceaccount key).
-4. In `/etc/kubernetes/apiserver`, ensure `KUBE_API_ARGS` contains `--allow-privileged`
+0. In `/etc/kubernetes/kubelet`, ensure `KUBELET_ARGS` contains `--allow-privileged`
+0. On the master node, generate a default serviceaccount key with `openssl genrsa -out /tmp/serviceaccount.key 2048`
+0. In `/etc/kubernetes/apiserver`, ensure `KUBE_API_ARGS` contains `--service_account_key_file=/tmp/serviceaccount.key` (or the correct path to your default serviceaccount key).
+0. In `/etc/kubernetes/apiserver`, ensure `KUBE_API_ARGS` contains `--allow-privileged`
 
 ### Prepare cluster for use with ManageIQ
 
-1. Create `management-infra` namespace:
+0. Create `management-infra` namespace:
 
     ```bash
     kubectl create ns management-infra
     ```
 
-2. Create required serviceaccounts:
+0. Create required serviceaccounts:
 
     ```bash
-    kubectl create sa -n management-infra management-admin
-    kubectl create sa -n management-infra inspector-admin
+    kubectl create sa -n management-infra management-admin   
+    kubectl create sa -n management-infra inspector-admin   
     ```
 
-3. Grant cluster-reader cluster role to `management-admin` SA:
+0. Grant cluster-reader cluster role to `management-admin` SA:
 
     ```bash
     kubectl create clusterrolebinding management-infra-cluster-reader --clusterrole=cluster-reader --user=system:serviceaccount:management-infra:management-admin
     ```
 
-4. Retrieve the serviceaccount token for `management-admin` (this will be the auth token ManageIQ uses):
+0. Retrieve the serviceaccount token for `management-admin` (this will be the auth token ManageIQ uses):
 
     ```bash
     kubectl describe secret -n management-infra $(kubectl get secrets -n management-infra | grep management-admin | cut -f1 -d ' ') | grep -E '^token' | cut -f2 -d':' | tr -d '\t'

providers/subclassing_an_existing_provider.md

@@ -59,7 +59,7 @@ Follow the steps from [Creating a new provider](writing_a_new_provider.md) for s
 
 You'll notice however that we chose "--no-scaffolding" option, this is going to allow us to define the classes that we need as subclasses of the OpenStack provider.
 
-### Creating the Manager class
+### Creating the subclasses
 
 Now that we have an empty plugin we have to start adding the subclasses that we need for the provider to work.
 

ui/menus.md

@@ -24,7 +24,7 @@ Menu sections looks like the example above. It consists of:
 
 Identifier is the same as the [RBAC feature](rbac_features.md) that is checked when a decision is made whether or not the particular section is displayed.
 
-Text needs to be marked for translation but not translated at the time of definition, therefor ``N_`` see [I18n](../i18n.md)
+Text needs to be marked for translation but not translated at the time of definition, therefor ``N_`` see [I18n](i18n.md)
 
 Menu section structure (tree) forms the base of the RBAC tree that is available in the Role Editor. (See [RBAC features](rbac_features.md).)