diff --git a/_posts/2023-10-26-taxonworks-together.md b/_posts/2023-10-26-taxonworks-together.md
index 6dc2684..3422d8e 100644
--- a/_posts/2023-10-26-taxonworks-together.md
+++ b/_posts/2023-10-26-taxonworks-together.md
@@ -24,7 +24,7 @@ We presented echinopscis in the symposium session "The evolving landscape of bio
 
 ### Relations to TaxonWorks
 
-Local storage means that there is an opportunity to use as a starting point - users could initially work in echinopscis and then "upscale" into taxonworks and as a "safe haven" - prove that a data download from taxonworks could be used in a standalone echinopscis environment
+Local storage means that there is an opportunity to use (i) as a starting point - users could initially work in echinopscis and then "upscale" into taxonworks and (ii) as a "safe haven" - to show that a data download from taxonworks could be used in a standalone echinopscis environment.
 
 TaxonWorks also represents a valuable source of data that echinopscis should be able to interact with.
 
@@ -35,19 +35,19 @@ More fundamentally - the use of technologies like github pages (used for TaxonPa
 We then posed a couple of discussion points - (i) widescale adoption of the reconciliation API and (ii) enabling the navigation of linked data.
 
 **Reconciliation API** (or “strings to things”): the echinopscis demo shows multiple workflows where a user translates a piece of text (like a specimen reference) into an entity managed by an external authority (like a specimen record). Many users may be aware of the reconciliation process in Open Refine (a tool for manipulating messy data). This Open Refine Reconciliation API is now documented as a [standard](https://www.w3.org/community/reports/reconciliation/CG-FINAL-specs-0.2-20230410/) and can be implemented more widely. Some current data provider examples include:
-- Bionomia: https://bionomia.net/reconcile 
-- Catalogue of Life: https://github.com/CatalogueOfLife/backend/issues/1265 
-- Datasette (generic): https://github.com/drkane/datasette-reconcile 
+- Bionomia: [bionomia.net/reconcile](https://bionomia.net/reconcile) 
+- Catalogue of Life: [github.com/CatalogueOfLife/backend/issues/1265 ](https://github.com/CatalogueOfLife/backend/issues/1265)
+- Datasette (generic): [github.com/drkane/datasette-reconcile](https://github.com/drkane/datasette-reconcile) 
 And some examples of data consumers (developers of taxonomic / data manipulation tools) include:
-- Open Refine: https://openrefine.org/docs/manual/reconciling 
-- Python: https://github.com/jvfe/reconciler 
+- Open Refine: [openrefine.org/docs/manual/reconciling](https://openrefine.org/docs/manual/reconciling) 
+- Python: [github.com/jvfe/reconciler](https://github.com/jvfe/reconciler) 
 
 So - could we build an Obsidian plugin to faciliate turning "strings to things"?
 
 **Navigating linked data**
 “[entity explosion](https://github.com/99of9/Entity-Explosion)” is a browser plugin that shows links from Wikidata based on the currently loaded page. Here is an example of an author profile page from the International Plant Names Index, showing data retrieved from WikiData via this extension:
 
-![Screenshot of entity explosion browser plugin operating on an author profile page from the Inetrnational Plant Names Index](/assets/taxonworks-together-2023/entity-explosion-example.jpg)
+![Screenshot of entity explosion browser plugin operating on an author profile page from the International Plant Names Index](/assets/images/taxonworks-together-2023/entity-explosion-example.jpg)
 
 Could we develop equivalents for:
 - Obsidian - using an ID stored in page frontmatter to run a Wikidata query and show useful links in a sidebar
@@ -56,4 +56,5 @@ Could we develop equivalents for:
 
 ## Useful links
 
-- Slidedeck (link TBC)
+- Slidedeck (link TBC), talk recording (link TBC)
+- echinopscis discussion board: [github.com/orgs/echinopscis/discussions](https://github.com/orgs/echinopscis/discussions)