diff --git a/.github/PULL_REQUEST_TEMPLATE/community_contribution.md b/.github/PULL_REQUEST_TEMPLATE/community_contribution.md
index 87de025..0aa1e06 100644
--- a/.github/PULL_REQUEST_TEMPLATE/community_contribution.md
+++ b/.github/PULL_REQUEST_TEMPLATE/community_contribution.md
@@ -1,7 +1,7 @@
 ---
 
 name: Contribution of a new provider
-about: Contributing additional providers to a xyzservices-providers.JSON
+about: Contributing additional providers to an xyzservices-providers.JSON
 title: "PRO:"
 labels: "community_contribution"
 
diff --git a/doc/source/introduction.ipynb b/doc/source/introduction.ipynb
index fa69fe1..eaa96da 100644
--- a/doc/source/introduction.ipynb
+++ b/doc/source/introduction.ipynb
@@ -188,7 +188,7 @@
     "\n",
     "Some packages like `contextily` can use `xyzservices.TileProvider` directly and parse the required information under the hood. Others need and explicit URL string, attribution and other attributes. However, not every package need the URL in the same format. `xyzsevices` can build the URL in most of the required formats, with or without placeholders.\n",
     "\n",
-    "Typical use case would be a folium map, which needs an URL and an attribution with `{x}`, `{y}` and `{z}` placeholders but already filled API keys if needed. You can get the most standard URL in the  `'https://myserver.com/tiles/{z}/{x}/{y}.png'` format via `TileProvider.build_url()`. And if you want a sharper resolution (when supported by the provider), you can pass an optional `scale_factor` attribute."
+    "Typical use case would be a folium map, which needs a URL and an attribution with `{x}`, `{y}` and `{z}` placeholders but already filled API keys if needed. You can get the most standard URL in the  `'https://myserver.com/tiles/{z}/{x}/{y}.png'` format via `TileProvider.build_url()`. And if you want a sharper resolution (when supported by the provider), you can pass an optional `scale_factor` attribute."
    ],
    "metadata": {}
   },