Skip to content

Commit

Permalink
Fix some xrefs
Browse files Browse the repository at this point in the history
  • Loading branch information
astrojuanlu committed Jul 24, 2022
1 parent 4e01960 commit b2556f6
Show file tree
Hide file tree
Showing 4 changed files with 4 additions and 4 deletions.
2 changes: 1 addition & 1 deletion docs/source/development/concepts_in_orchest.md
Expand Up @@ -27,7 +27,7 @@ Projects
Projects. You can think of a Project as a folder on your filesystem that contains a bunch of
Files, some of which are "special" (hinting at Pipeline files with a `.orchest` extension). In
addition to the filesystem state, Orchest saves state in a database. This state includes things
such as {ref}`environment variables <environment variables>`.
such as {ref}`environment variables <environment-variables>`.

```{image} ../img/concepts/Project.png
:width: 200
Expand Down
2 changes: 1 addition & 1 deletion docs/source/fundamentals/jobs.md
Expand Up @@ -84,7 +84,7 @@ You can think of job parameters as a [grid search](https://scikit-learn.org/stab
i.e. looping over all combinations of values for different parameters.

```{note}
💡 Unlike {ref}`environment variables <environment variables>`, you can define
💡 Unlike {ref}`environment variables <environment-variables>`, you can define
pipeline and step level parameters with the same name without one (automatically) overwriting
the other, you can access both values.
```
Expand Down
2 changes: 1 addition & 1 deletion docs/source/fundamentals/pipelines.md
Expand Up @@ -52,7 +52,7 @@ Pipelines take parameters as input (e.g. the data source connection URL) to vary
pipeline. Parameters can be set in the visual pipeline editor.

```{tip}
👉 For secrets, use {ref}`environment variables <environment variables>` since parameters are versioned.
👉 For secrets, use {ref}`environment variables <environment-variables>` since parameters are versioned.
```

## Data passing
Expand Down
2 changes: 1 addition & 1 deletion docs/source/fundamentals/projects.md
Expand Up @@ -45,7 +45,7 @@ A project's `.orchest` directory should be versioned since it defines the {ref}`

The `/data` directory can be used to store data locally that is accessible by all pipelines across all projects, even by jobs.

Secrets should be set with {ref}`environment variables <environment variables>` to avoid them being versioned.
Secrets should be set with {ref}`environment variables <environment-variables>` to avoid them being versioned.

(git-inside-orchest)=

Expand Down

0 comments on commit b2556f6

Please sign in to comment.