diff --git a/docs/tutorials/99_other/getting_started_with_OEMetadata.ipynb b/docs/tutorials/99_other/getting_started_with_OEMetadata.ipynb
index e435b6a1..4bf08442 100644
--- a/docs/tutorials/99_other/getting_started_with_OEMetadata.ipynb
+++ b/docs/tutorials/99_other/getting_started_with_OEMetadata.ipynb
@@ -35,7 +35,7 @@
         "\n",
         "### Introduction\n",
         "\n",
-        "OpenenEnergyMetadata(OEM) is a standardised metadata format. OEM are used to provide relevant information about a dataset on the OEP \"It´s data explaining the data :)\". OEM are mandatory for oficially publishing data on the OEP, because this will clarify any licensing issues in advance and also provide context for the review that is part of every publishing process. You can find more information about publishing your data in the [publishing guidebook](https://openenergyplatform.github.io/academy/tutorials/99_other/OEP_Research_Data_Publishing_Guidebook/). There are descriptions on how to upload OEM on the Open Energy Platform itself with a [wizard](https://openenergyplatform.org/dataedit/wizard/) and a more [technical description](https://openenergyplatform.github.io/academy/tutorials/02_oep_client/02_client_python_upload/)) for using the API in scrips. If a dataset has already been uploaded to the OEP, then the metadata can be viewed via the [detailed view](https://openenergyplatform.org/dataedit/view/climate/szenariendb_gwp#MetaInformation) of a table. You just scroll down to the \"Meta Information\" section and there they are. The OEP also offers functions for creating, editing and downloading metadata. These functions can also be found on the detail view. Make sure to [sign in](https://openenergyplatform.org/user/login/?next=/) to the OEP in advance to get writing access.\n",
+        "OpenenEnergyMetadata(OEM) is a standardised metadata format. OEM are used to provide relevant information about a dataset on the OEP \"It´s data explaining the data :)\". OEM are mandatory for oficially publishing data on the OEP, because this will clarify any licensing issues in advance and also provide context for the review that is part of every publishing process. You can find out how to publish your data in the [publishing guidebook](https://openenergyplatform.github.io/academy/tutorials/99_other/OEP_Research_Data_Publishing_Guidebook/). There are descriptions on how to upload OEM on the Open Energy Platform itself with a [wizard](https://openenergyplatform.github.io/academy/tutorials/99_other/wizard/#upload-a-csv-file-using-the-wizard) and a more [technical description](https://openenergyplatform.github.io/academy/tutorials/02_oep_client/02_client_python_upload/)) for using the API in scrips. If a dataset has already been uploaded to the OEP, then the metadata can be seen in the [view of the table](https://openenergyplatform.org/dataedit/view/climate/szenariendb_gwp) by clicking on the tab `Meta Information` right next to `Data`. The OEP also offers functions for editing and downloading metadata, which can be accessed in the Meta Information view . Make sure to [sign in](https://openenergyplatform.org/user/login/?next=/) to the OEP in advance to be able to edit the data. You can see what permissions you have in the options on the rigth hand side by clicking on [Permissions](https://openenergyplatform.org/dataedit/view/climate/szenariendb_gwp/permissions).\n",
         "\n",
         "### Compatible with frictionless data\n",
         "\n",