diff --git a/packages/repository/README.md b/packages/repository/README.md
index cbe058abe3ce..242741cae871 100644
--- a/packages/repository/README.md
+++ b/packages/repository/README.md
@@ -72,8 +72,8 @@ export class NoteRepository extends DefaultCrudRepository<
   Note,
   typeof Note.prototype.id
 > {
-  constructor(@inject('datasources.db') protected datasource: DataSourceType) {
-    super(Note, datasource);
+  constructor(@inject('datasources.db') protected dataSource: DataSourceType) {
+    super(Note, dataSource);
   }
 }
 ```
@@ -164,7 +164,7 @@ against the underlying database or service.
 `Repository` can be defined and implemented by application developers. LoopBack
 ships a few predefined `Repository` interfaces for typical CRUD and KV
 operations. These `Repository` implementations leverage `Model` definition and
-`Datasource` configuration to fulfill the logic for data access.
+`DataSource` configuration to fulfill the logic for data access.
 
 ```js
 interface Repository<T extends Model> {}
@@ -229,9 +229,9 @@ There are two subtly different types of models for domain objects:
   }
   ```
 
-### Datasource
+### DataSource
 
-`Datasource` is a named configuration of a connector. The configuration
+`DataSource` is a named configuration of a connector. The configuration
 properties vary by connectors. For example, a datasource for `MySQL` needs to
 set the `connector` property to `loopback-connector-mysql` with settings as
 follows:
@@ -246,7 +246,7 @@ follows:
 }
 ```
 
-When a `Datasource` is instantiated, the configuration properties will be used
+When a `DataSource` is instantiated, the configuration properties will be used
 to initialize the connector to connect to the backend system.
 
 ### Connector