small rewordings

ricardo-devis-agullo · ricardo-devis-agullo · commit b94f449b4c07 · 2025-07-21T09:02:30.000+02:00
diff --git a/website/docs/building/template-system.md b/website/docs/building/template-system.md
@@ -14,7 +14,7 @@ Within the component's `package.json` a template type need to be specified toget
 
 > By convention the compiler need to follow the naming structure: **`<template-type>-compiler`**.
 
-For example a component of type: `oc-template-handlebars` will need a compiler named `oc-template-handlebars-compiler` in order to be correctly packaged and published:
+For example a component of type: `oc-template-es6` will need a compiler named `oc-template-es6-compiler` **so it can be** correctly packaged and published:
 
 ```json
 ...
diff --git a/website/docs/components/cli.md b/website/docs/components/cli.md
@@ -182,7 +182,7 @@ $ oc clean ../all-components --yes
 
 ### dev
 
-Runs a local oc test registry in order to develop and test components
+Runs a local oc test registry **to develop and test components**
 
 #### Usage:
 
@@ -251,7 +251,7 @@ which will create `test-component` in `components` directory.
 
 ### mock
 
-Allows to mock configuration in order to facilitate local development
+Allows **mocking configuration to simplify local development**
 
 #### Usage
 
diff --git a/website/docs/consumers/client-side-rendering.md b/website/docs/consumers/client-side-rendering.md
@@ -34,9 +34,9 @@ This is how to integrate the component:
 5. In case of error (timeout or 5xx response) the client is going to retry 30 times (retry attempts and timeout are configurable)
 6. In case of success, the client is going to find what kind of template the component uses and verify dependencies are satisfied. For ES6 templates (the default), it ensures the template function is ready. For legacy template types like Handlebars, it ensures the respective runtime is available and ready, downloading it if necessary before proceeding to the next step
 7. The client will take the compiled view url, for instance `//cdn.com/components/my-component/1.2.3/template.js` and put it in the `<head>` tag, then waiting for it to be ready. If the template is already there (for example because there are multiple components of the same type and version in the page) it is going to skip step 7. When the template is ready it is exposed in the `window.oc.components['hash-of-the-component']` namespace as a function: `view(viewModel)=html`.
-8. This is going to take the viewModel (part of the HTTP response) and use it to render the view, in order to obtain the html. When finished, it is going to place the HTML result inside the `<oc-component>` container tag. Some templates may perform additional actions. In case of a React template, for instance, the HTML may be bound to the Virtual DOM.
+8. This is going to take the viewModel (part of the HTTP response) and use it to render the view, **producing** the HTML. When finished, it places the HTML result inside the `<oc-component>` container tag. Some templates may perform additional actions. In case of a React template, for instance, the HTML may be bound to the Virtual DOM.
 9. An `oc:rendered` event is published containing the pointer to the component, and all the information (version, name, html, etc.)
-10. Back to 3) In order to render, in case, nested client-side components
+10. Back to 3) **To render nested client-side components, if any are present**
 
 ## What can I do in the client-side?
 
diff --git a/website/docs/intro.md b/website/docs/intro.md
@@ -115,7 +115,7 @@ Now, it should be available at `http://my-components-registry.mydomain.com/hello
 
 # Consuming Components
 
-From a consumer's perspective, a component is an HTML fragment. You can render components just on the client-side, just on the server-side, or use the client-side rendering as failover strategy for when the server-side rendering fails (for example because the registry is not responding quickly or is down).
+From a consumer's perspective, a component is an HTML fragment. You can render components **client-side, server-side, or fall back to client-side rendering** when server-side rendering fails (for example, if the registry is slow or unavailable).
 
 You don't need Node.js to consume components on the server-side. The registry can provide you rendered components so that you can consume them using any tech stack.
 
