diff --git a/UPGRADE.md b/UPGRADE.md
index 58d3e41be1b..21cdff83f10 100644
--- a/UPGRADE.md
+++ b/UPGRADE.md
@@ -645,7 +645,7 @@ const i18nProvider = {
             // load new messages and update the translate function
         })
     },
-    getLocale: () => locale;
+    getLocale: () => locale
 } 
 ```
 
diff --git a/docs/Authentication.md b/docs/Authentication.md
index c363fbb6ed0..18e1d84d350 100644
--- a/docs/Authentication.md
+++ b/docs/Authentication.md
@@ -271,7 +271,7 @@ export default {
 
 ### Logout Configuration
 
-If you enable authentication, react-admin adds a logout button in the user menu in the top bar (or in the sliding menu on mobile. When the user clicks on the logout button, this calls the `authProvider.logout()` method, and removes potentially sensitive data from the Redux store. Then the user gets redirected to the login page. The two previous sections also illustrated that react-admin can call `authProvider.logout()` itself, when the API returns a 403 error or when the local credentials expire. 
+If you enable authentication, react-admin adds a logout button in the user menu in the top bar (or in the sliding menu on mobile). When the user clicks on the logout button, this calls the `authProvider.logout()` method, and removes potentially sensitive data from the Redux store. Then the user gets redirected to the login page. The two previous sections also illustrated that react-admin can call `authProvider.logout()` itself, when the API returns a 403 error or when the local credentials expire. 
 
 It's the responsibility of the `authProvider.logout()` method to clean up the current authentication data. For instance, if the authentication was a token stored in local storage, here is the code to remove it:
 
diff --git a/docs/Fields.md b/docs/Fields.md
index a320b3e9aa0..279f9fd8ad6 100644
--- a/docs/Fields.md
+++ b/docs/Fields.md
@@ -539,7 +539,7 @@ import { TextField } from 'react-admin';
 
 ### `<UrlField>`
 
-`<UrlField>` displays an url in a Material UI's `<Link href="" />` component.
+`<UrlField>` displays a url in a Material UI's `<Link href="" />` component.
 
 ```jsx
 import { UrlField } from 'react-admin';
diff --git a/docs/Tutorial.md b/docs/Tutorial.md
index f7c88d7ce3c..3505169f880 100644
--- a/docs/Tutorial.md
+++ b/docs/Tutorial.md
@@ -200,7 +200,7 @@ What you've just done reflects the early stages of development with react-admin:
 
 You've just met the `<TextField>` and the `<EmailField>` components. React-admin provides [many more Field components](./Fields.md), mapping various data types: number, date, image, HTML, array, reference, etc.
 
-For instance, the `website` field looks like an URL. Instead of displaying it as text, why not display it using a clickable link? That's exactly what the `<UrlField>` does:
+For instance, the `website` field looks like a URL. Instead of displaying it as text, why not display it using a clickable link? That's exactly what the `<UrlField>` does:
 
 ```diff
 // in src/users.js
diff --git a/packages/ra-core/src/inference/inferElementFromValues.spec.tsx b/packages/ra-core/src/inference/inferElementFromValues.spec.tsx
index b318ef33710..74bf6e5d7e2 100644
--- a/packages/ra-core/src/inference/inferElementFromValues.spec.tsx
+++ b/packages/ra-core/src/inference/inferElementFromValues.spec.tsx
@@ -187,7 +187,7 @@ describe('inferElementFromValues', () => {
             ).getElement()
         ).toEqual(<Good source="foo" />);
     });
-    it('should return an url field for url name', () => {
+    it('should return a url field for url name', () => {
         const types = {
             url: { component: Good },
             string: { component: Bad },
@@ -200,7 +200,7 @@ describe('inferElementFromValues', () => {
             ).getElement()
         ).toEqual(<Good source="url" />);
     });
-    it.skip('should return an url field for url string values', () => {
+    it.skip('should return a url field for url string values', () => {
         const types = {
             url: { component: Good },
             string: { component: Bad },
diff --git a/packages/ra-core/src/inference/inferTypesFromValues.spec.ts b/packages/ra-core/src/inference/inferTypesFromValues.spec.ts
index 711c41a72ee..44828ab1222 100644
--- a/packages/ra-core/src/inference/inferTypesFromValues.spec.ts
+++ b/packages/ra-core/src/inference/inferTypesFromValues.spec.ts
@@ -102,13 +102,13 @@ describe('inferTypeFromValues', () => {
             props: { source: 'foo' },
         });
     });
-    it('should return an url field for url name', () => {
+    it('should return a url field for url name', () => {
         expect(inferTypeFromValues('url', ['whatever', 'whatever'])).toEqual({
             type: 'url',
             props: { source: 'url' },
         });
     });
-    it.skip('should return an url field for url string values', () => {
+    it.skip('should return a url field for url string values', () => {
         expect(
             inferTypeFromValues('foo', [
                 'http://foo.com/bar',