summaryrefslogtreecommitdiff
path: root/_i18n
diff options
context:
space:
mode:
authorHombreLaser <sebastian-440@live.com>2023-08-30 22:55:14 -0600
committerHombreLaser <sebastian-440@live.com>2023-08-30 22:55:14 -0600
commitf0db0574f3c3a8074842c17a82623c9aa6aafd82 (patch)
tree37d7a5a7acddbad52f56f783ad11075900cee707 /_i18n
parentecebb1136ea5c56710268b40b0451744fec51a82 (diff)
Add deploy test
Diffstat (limited to '_i18n')
-rw-r--r--_i18n/es/_posts/2023-08-27-welcome-to-jekyll.markdown2
1 files changed, 1 insertions, 1 deletions
diff --git a/_i18n/es/_posts/2023-08-27-welcome-to-jekyll.markdown b/_i18n/es/_posts/2023-08-27-welcome-to-jekyll.markdown
index cfe9444..1e40ecd 100644
--- a/_i18n/es/_posts/2023-08-27-welcome-to-jekyll.markdown
+++ b/_i18n/es/_posts/2023-08-27-welcome-to-jekyll.markdown
@@ -5,7 +5,7 @@ date: 2023-08-27 08:17:42 +0000
categories: jekyll update
---
Esta es una prueba. Esta es otra. Veamos si se ejecuta.
-Por favor funciona.
+Ya corregí los permisos, funcionará ésta vez?
You’ll find this post in your `_posts` directory. Go ahead and edit it and re-build the site to see your changes. You can rebuild the site in many different ways, but the most common way is to run `jekyll serve`, which launches a web server and auto-regenerates your site when a file is updated.
Jekyll requires blog post files to be named according to the following format: