let's full paths

Author: maciejkorsan

railseventstore.org/docs/getting-started/introduction.md

@@ -19,18 +19,18 @@ rails new -m https://railseventstore.org/new YOUR-APP-NAME
 
 ## What next?
 
-- check Rails Event Store setup defined in `config/initializers/rails_event_store.rb`, learn more how to setup Rails Event Store [here](./install/)
-- decide if default `YAML` serialization suits your needs, see more about serialization formats [here](../advanced-topics/event-serialization-formats)
+- check Rails Event Store setup defined in `config/initializers/rails_event_store.rb`, learn more how to setup Rails Event Store [here](/docs/getting-started/install/)
+- decide if default `YAML` serialization suits your needs, see more about serialization formats [here](/docs/advanced-topics/event-serialization-formats)
 - start implementing your domain, use `bounded_context` gem's generators to initialize folders structure for your domain model (use `rails generate rails_event_store:bounded_context YOUR-BOUNDED-CONTEXT-NAME` command)
-- implement your aggregates using `AggregateRoot` module, see how [here](../core-concepts/event-sourcing)
-- subscribe to domain events published, [check how](../core-concepts/subscribe) to define subscriptions and event handlers
-- learn Command pattern and [how to](../advanced-topics/command-bus) use Arkency's command bus to decouple your domain model from controllers
-- check [how to](../core-concepts/rspec) use provided `RSpec` matchers
+- implement your aggregates using `AggregateRoot` module, see how [here](/docs/core-concepts/event-sourcing)
+- subscribe to domain events published, [check how](/docs/core-concepts/subscribe) to define subscriptions and event handlers
+- learn Command pattern and [how to](/docs/advanced-topics/command-bus) use Arkency's command bus to decouple your domain model from controllers
+- check [how to](/docs/core-concepts/rspec) use provided `RSpec` matchers
 - learn more about:
-  - [reading](../core-concepts/read) domain events
-  - [publishing](../core-concepts/publish) domain events
-  - logging [request metadata](../core-concepts/request-metadata)
-  - concurrencycontrol using [expected version](../core-concepts/expected-version)
-  - possible [errors](../core-concepts/client-errors)
+  - [reading](/docs/core-concepts/read) domain events
+  - [publishing](/docs/core-concepts/publish) domain events
+  - logging [request metadata](/docs/core-concepts/request-metadata)
+  - concurrency control using [expected version](/docs/core-concepts/expected-version)
+  - possible [errors](/docs/core-concepts/client-errors)
 
-API documentation is available [here](./api)
+API documentation is available [here](/docs/getting-started/api)