Fix links

Author: kabilar

docs/src/design/schema.md

@@ -44,6 +44,6 @@ database and will raise errors when accessing missing tables.
 
 ## Working with existing data
 
-See the chapter [existing](../existing-pipelines.md) for how to work with data in 
+See the chapter [recall](recall.md) for how to work with data in 
 existing pipelines, including accessing a pipeline from one language when the pipeline 
 was developed using another.

docs/src/design/tables/filepath.md

@@ -12,8 +12,8 @@ tables to reference data which lives outside of the DataJoint
 pipeline.
 
 To define a table using the `filepath` datatype, an existing DataJoint
-[store](../../sysadmin/filestore.md) should be created and then referenced in the new
-table definition. For example, given a simple store:
+[store](../../sysadmin/external-store.md) should be created and then referenced in the 
+new table definition. For example, given a simple store:
 
 ```json
 dj.config['stores'] = {

docs/src/query/fetch.md

@@ -3,7 +3,7 @@
 Data queries in DataJoint comprise two distinct steps:
 
 1. Construct the `query` object to represent the required data using tables and 
-[operators](operators.m`).
+[operators](operators.md).
 2. Fetch the data from `query` into the workspace of the host language -- described in 
 this section.
 

docs/src/quick-start.md

@@ -189,7 +189,7 @@ This can be done for an entire schema:
 dj.Diagram(schema)
 ```
 
-![pipeline](../images/shapes_pipeline.svg)
+![pipeline](./images/shapes_pipeline.svg)
 
 Or for individual or sets of tables:
 ```python