Fix README typos

README.md

@@ -1,14 +1,14 @@
 # rml-utils-processor-ts
 
-[![Bun CI](https://github.com/julianrojas87/rml-utils-processor-ts/actions/workflows/build-test.yml/badge.svg)](https://github.com/julianrojas87/rml-utils-processor-ts/actions/workflows/build-test.yml) [![npm](https://img.shields.io/npm/v/@rdfc/rml-utils-processor-ts.svg?style=popout)](https://npmjs.com/package/@rdfc/rml-utils-processor-ts)
+[![Bun CI](https://github.com/rdf-connect/rml-utils-processor-ts/actions/workflows/build-test.yml/badge.svg)](https://github.com/rdf-connect/rml-utils-processor-ts/actions/workflows/build-test.yml) [![npm](https://img.shields.io/npm/v/@rdfc/rml-utils-processor-ts.svg?style=popout)](https://npmjs.com/package/@rdfc/rml-utils-processor-ts)
 
 Collection of Typescript utilities around RML (RDF Mapping Language) tools that includes a wrapper over the RML Mapper to be reused within the [RDF-Connect](https://rdf-connect.github.io/rdfc.github.io/) ecosystem  Currently this repository exposes 3 processors:
 
-### [`js:Y2R`](https://github.com/julianrojas87/rml-utils-processor-ts/blob/main/processors.ttl#L9)
+### [`js:Y2R`](https://github.com/rdf-connect/rml-utils-processor-ts/blob/main/processors.ttl#L9)
 
 This processor takes a stream of YARRRML mapping files as input and converts them to their correspondent representation in RML quads. It relies on the [`yarrrml-parser`](https://github.com/RMLio/yarrrml-parser) library for executing the transformation.
 
-### [`js:RMLMapperReader`](https://github.com/julianrojas87/rml-utils-processor-ts/blob/main/processors.ttl#L44)
+### [`js:RMLMapperReader`](https://github.com/rdf-connect/rml-utils-processor-ts/blob/main/processors.ttl#L44)
 
 This processor executes RML mapping rules using the Java-based [RMLMapper engine](https://github.com/RMLio/rmlmapper-java). A mapping process can be defined within a RDF-Connect (RDF-C) pipeline, by defining an input stream of RML mappings, which will be executed sequentially. A default writer channel (`js:output`) needs to be defined, where all produced RDF triples/quads will be streamed, from mappings that do not define explicit Logical Targets. A set of logical sources (`js:rmlSource`) and targets (`js:rmlTarget`) can be optionally declared to make them visible to the RDF-C pipeline.
 
@@ -36,7 +36,7 @@ Logical sources can be marked as trigger-based (`js:trigger`) to indicate that t
     js:rmlJar <./rmlmapper-6.3.0-r0-all.jar>.
 ```
 
-### [`js:IncRMLTransformer`](https://github.com/julianrojas87/rml-utils-processor-ts/blob/main/processors.ttl#L142)
+### [`js:IncRMLTransformer`](https://github.com/rdf-connect/rml-utils-processor-ts/blob/main/processors.ttl#L142)
 
 This processor transforms a given stream of RML mapping documents to their correspondent Incremental RML (IncRML) representation. Concretely, this means that every defined `rr:TriplesMap` (that has at least 1 defined `rr:predicateObjectMap`) is further expanded into 3 new `rr:TriplesMap`s, each one dedicated to handle entity `create`, `update` and `delete` events. The processor will merge Triple Maps that produce the same Subject IRI, use the same Logical Source and belong to the same Named Graph (if any).