Actual Behaviour: 

In https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-1084/plugins-rhdh-install/#rhdh-extensions-plugins-installing_rhdh-extensions-plugins the docs are ambiguous and could be more specific that "Extensions" is a very specific thing when referenced here. It's a generic word that would benefit from more context to ensure the user understands what it means and where they need to go.

Expected Behaviour: 

Adding "catalog" or some other qualifer after Extensions, at least when introducing it, would help clear up potential ambiguity. 

Additional information: 

Actual: The screenshot here https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-1084/plugins-rhdh-install/images/rhdh-plugins-reference/rhdh-extensions-tekton-card.png doesn't include the blue highlight on the Extensions nav item in the sidebar, which makes it harder to understand from the screenshot where they are in the UI, or how they got there, if the procedure doesn't specify a starting point. The Tekton displayed is also the Community version, and what we see in test day is the Red Hat provided option, which has a different icon. I don't see the community version listed. 

Expected: 

Navigational elements in the UI to be visible in the screenshots and match what users will see, wherever possible.

https://drive.google.com/file/d/1NpDS3MGhNyoLcBpoNVKR4iNsAOTr_73m/view

https://drive.google.com/file/d/149ebwnzHeJBGJkTiKmAJjWtnTLpN5Eu1/view 

Additional Information: 

In "4.5. Removing Extensions" there's no context on Extensions, and the location of the config file needed to edit to disable them is not mentioned

Consider adding catalog or some other qualifer to the section header. Extensions is a very generic word. Leaving the user to go find the config file they need to modify leaves them hanging and makes the procedure more difficult than if we suggested where they might find it.