From 999d277311798d5de109fe25ce0905507cf0f064 Mon Sep 17 00:00:00 2001 From: DorsetDigital Date: Thu, 14 Nov 2019 08:35:08 +0000 Subject: [PATCH] Change example domains The current examples use an actual, real-world domain. Have changed to the 'example.com' domain, reserved by IANA for this kind of purpose. --- docs/en/02_Developer_Guides/04_Configuration/01_SiteConfig.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/en/02_Developer_Guides/04_Configuration/01_SiteConfig.md b/docs/en/02_Developer_Guides/04_Configuration/01_SiteConfig.md index 6abbe4c3e..873aeba3c 100644 --- a/docs/en/02_Developer_Guides/04_Configuration/01_SiteConfig.md +++ b/docs/en/02_Developer_Guides/04_Configuration/01_SiteConfig.md @@ -73,8 +73,8 @@ Silverstripe\SiteConfig\SiteConfig: ```
-After adding the class and the YAML change, make sure to rebuild your database by visiting http://yoursite.com/dev/build. -You may also need to reload the screen with a `?flush=1` i.e http://yoursite.com/admin/settings?flush=1. +After adding the class and the YAML change, make sure to rebuild your database by visiting http://example.com/dev/build. +You may also need to reload the screen with a `?flush=1` i.e http://example.com/admin/settings?flush=1.
You can define as many extensions for `SiteConfig` as you need. For example, if you're developing a module and want to