A component has the below shown properties & methods available for use. As mentioned above, most of these should be used within the `setup()` function to make the requirements/dependencies of the component clear.
```javascript
-// The root element that the compontent has been applied to.
+// The root element that the component has been applied to.
this.$el
-// A map of defined element references within the compontent.
+// A map of defined element references within the component.
// See "Element References" above.
this.$refs
-// A map of defined multi-element references within the compontent.
+// A map of defined multi-element references within the component.
// See "Element References" above.
this.$manyRefs
-// Options defined for the compontent.
+// Options defined for the component.
this.$opts
// The registered name of the component, usually kebab-case.
```js
// HTTP service
+// Relative URLs will be resolved against the instance BASE_URL
window.$http.get(url, params);
window.$http.post(url, data);
window.$http.put(url, data);
// Translator
// Take the given plural text and count to decide on what plural option
// to use, Similar to laravel's trans_choice function but instead
-// takes the direction directly instead of a translation key.
-window.trans_plural(translationString, count, replacements);
+// takes the translation text directly instead of a translation key.
+window.$trans.choice(translationString, count, replacements);
// Component System
// Parse and initialise any components from the given root el down.
// Get the first active component of the given name that's been
// created on the given element.
window.$components.firstOnElement(element, name);
-```
\ No newline at end of file
+```
+
+## Public Events
+
+There are a range of available events that are emitted as part of a public & supported API for accessing or extending JavaScript libraries & components used in the system.
+
+Details on these events can be found in the [JavaScript Public Events file](javascript-public-events.md).