This is an automated email from the ASF dual-hosted git repository.

rombert pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-site.git


The following commit(s) were added to refs/heads/master by this push:
     new 6b21589  Fix broken link in discover sling docs (#9)
6b21589 is described below

commit 6b21589d3849cfc4578999c756187456b090ffe7
Author: John Bradley <[email protected]>
AuthorDate: Sat Feb 3 18:04:27 2018 -0500

    Fix broken link in discover sling docs (#9)
    
    The label was correct but the actual link didn't work.
---
 .../documentation/getting-started/discover-sling-in-15-minutes.md       | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/src/main/jbake/content/documentation/getting-started/discover-sling-in-15-minutes.md
 
b/src/main/jbake/content/documentation/getting-started/discover-sling-in-15-minutes.md
index f6be6d9..28ac7d4 100644
--- 
a/src/main/jbake/content/documentation/getting-started/discover-sling-in-15-minutes.md
+++ 
b/src/main/jbake/content/documentation/getting-started/discover-sling-in-15-minutes.md
@@ -151,7 +151,7 @@ Using cURL's *-D* option shows the full HTTP response, 
which includes a *Locatio
 
 The actual node name might not be *adventures_with_slin* - depending on 
existing content in your repository, Sling will find a unique name for this new 
node, based on several well-know property values like title, description, etc. 
which are used for this if provided.
 
-So, in our case, our new node can be displayed in HTML via the 
[http://localhost:8080/blog/adventures_with_slin.html](http://localhost:8080/blog/adventures*with*slin.html)
 URL.
+So, in our case, our new node can be displayed in HTML via the 
[http://localhost:8080/blog/adventures_with_slin.html](http://localhost:8080/blog/adventures_with_slin.html)
 URL.
 
 Note that we didn't set a *sling:resourceType* property on our node, so if you 
want to render that node with a script, you'll have to store the script under 
*/apps/nt/unstructured/html.esp*.
 

-- 
To stop receiving notification emails like this one, please contact
[email protected].

Reply via email to