From e446a281d4fefbc0335bee9e3ea9b9c0403498b9 Mon Sep 17 00:00:00 2001
From: pattiyaa <pattiyaa@gmail.com>
Date: Sun, 13 Sep 2020 23:45:02 +0700
Subject: [PATCH] correct spelling

---
 _includes/block.html             | 22 +++++------
 _includes/block_icon_cards.html  |  4 +-
 _includes/block_image_cards.html |  6 +--
 _includes/block_image_text.html  |  8 ++--
 _includes/block_text.html        |  2 +-
 _includes/block_text_cards.html  |  4 +-
 _includes/block_text_image.html  |  8 ++--
 index.markdown                   | 66 ++++++++++++++++----------------
 8 files changed, 60 insertions(+), 60 deletions(-)

diff --git a/_includes/block.html b/_includes/block.html
index 31f0e2a..8f4f75b 100644
--- a/_includes/block.html
+++ b/_includes/block.html
@@ -1,26 +1,26 @@
 {% case include.block.layout %}
   {% when "block_image_text" %}
     {% include block_image_text.html title=include.block.title paragraph=include.block.paragraph
-      image = include.block.image  button_lable=include.block.button_lable button_url=include.block.button_url 
+      image = include.block.image  button_label=include.block.button_label button_url=include.block.button_url 
       fluid=0 %}
   {% when "block_image_text_fluid" %}
     {% include block_image_text.html title=include.block.title paragraph=include.block.paragraph
-      image = include.block.image button_lable=include.block.button_lable button_url=include.block.button_url 
+      image = include.block.image button_label=include.block.button_label button_url=include.block.button_url 
       fluid=1 %}
   {% when "block_text_image" %}
     {% include block_text_image.html title=include.block.title paragraph=include.block.paragraph
-        image = include.block.image button_lable=include.block.button_lable button_url=include.block.button_url 
+        image = include.block.image button_label=include.block.button_label button_url=include.block.button_url 
         fluid=0 %}
   {% when "block_text_image_fluid" %}
     {% include block_text_image.html title=include.block.title paragraph=include.block.paragraph
-        image = include.block.image button_lable=include.block.button_lable button_url=include.block.button_url 
+        image = include.block.image button_label=include.block.button_label button_url=include.block.button_url 
         fluid=1 %}
   {% when "block_text" %}
-    {% include block_text.html  title=include.block.title paragraph=include.block.paragraph paragraph_aligh=include.block.paragraph_aligh
-          image = include.block.image image_size=include.block.image_size button_lable=include.block.button_lable button_url=include.block.button_url %}
+    {% include block_text.html  title=include.block.title paragraph=include.block.paragraph paragraph_align=include.block.paragraph_align
+          image = include.block.image image_size=include.block.image_size button_label=include.block.button_label button_url=include.block.button_url %}
   {% when "block_text_fluid" %}
-    {% include block_text.html  title=include.block.title paragraph=include.block.paragraph paragraph_aligh=include.block.paragraph_aligh
-      image = include.block.image image_size=include.block.image_size button_lable=include.block.button_lable button_url=include.block.button_url
+    {% include block_text.html  title=include.block.title paragraph=include.block.paragraph paragraph_align=include.block.paragraph_align
+      image = include.block.image image_size=include.block.image_size button_label=include.block.button_label button_url=include.block.button_url
       fluid=1 %}
   {% when "block_icon_cards" %}
     {% include block_icon_cards.html header=include.block.header  cards=include.block.cards card_per_line=include.block.card_per_line   %}
@@ -34,15 +34,15 @@
       {% include block_image_cards.html header=include.block.header cards=include.block.cards card_per_line=include.block.card_per_line  %}
   {% when "block_image" %}
     {% include block_image.html title=include.block.title paragraph=include.block.paragraph
-      image = include.block.image  button_lable=include.block.button_lable button_url=include.block.button_url 
+      image = include.block.image  button_label=include.block.button_label button_url=include.block.button_url 
       fluid=0 %}
   {% when "block_image_fluid" %}
     {% include block_image.html title=include.block.title paragraph=include.block.paragraph
-      image = include.block.image button_lable=include.block.button_lable button_url=include.block.button_url 
+      image = include.block.image button_label=include.block.button_label button_url=include.block.button_url 
       fluid=1 %}
   {% when "block_image_banner" %}
     {% include block_image.html title=include.block.title paragraph=include.block.paragraph
-      image = include.block.image button_lable=include.block.button_lable button_url=include.block.button_url 
+      image = include.block.image button_label=include.block.button_label button_url=include.block.button_url 
     %}
   {% when "block_contactus_mascot" %}
     {% include block_contactus_mascot.html  form_input=include.block.form_input button_label=include.block.button_label %}
diff --git a/_includes/block_icon_cards.html b/_includes/block_icon_cards.html
index 2818cf7..261165f 100644
--- a/_includes/block_icon_cards.html
+++ b/_includes/block_icon_cards.html
@@ -43,9 +43,9 @@ <h3>{{item.title}}</h3>
           {% else %}
             {% assign buttonClassName = "button" %}
           {% endif %}
-          {% if item.button_url && item.button_lable  %}
+          {% if item.button_url && item.button_label  %}
              <a class="{{ buttonClassName}}"
-              href="{{ item.button_url }}">{{ item.button_lable }}</a>
+              href="{{ item.button_url }}">{{ item.button_label }}</a>
           {% endif %}
           </div>
         </div>
diff --git a/_includes/block_image_cards.html b/_includes/block_image_cards.html
index 1c25823..499c5a2 100644
--- a/_includes/block_image_cards.html
+++ b/_includes/block_image_cards.html
@@ -13,7 +13,7 @@ <h2>{{include.header.title}}</h2>
       divided_by: card_per %} {% assign divConClassName = "col-lg-" | append:
       col %} {% else %} {% assign divConClassName = "col-lg" %} {% endif %}
       <div class="col-md-6 {{ divConClassName }}  mb-4 mb-lg-4">
-        {% if item.button_lable %}
+        {% if item.button_label %}
         <div class="card-blog">
           <img class="card-img rounded-0" src="{{item.image}}" alt="" />
           <div class="card-blog-body">
@@ -24,9 +24,9 @@ <h4>{{item.title}}</h4>
             {% else %}
               {% assign buttonClassName = "button" %}
             {% endif %}
-            {% if item.button_url && item.button_lable  %}
+            {% if item.button_url && item.button_label  %}
             <a class="{{ buttonClassName}}" href="{{ item.button_url }}"
-              >{{ item.button_lable }}</a >
+              >{{ item.button_label }}</a >
             {% endif %}
           </div>
         </div>
diff --git a/_includes/block_image_text.html b/_includes/block_image_text.html
index 26c39e6..9eb994f 100644
--- a/_includes/block_image_text.html
+++ b/_includes/block_image_text.html
@@ -20,8 +20,8 @@ <h2>{{ include.title }}</h2>
             {% else %}
               {% assign buttonClassName = "button" %}
             {% endif %}
-            {% if item.button_url && item.button_lable  %}
-            <a class="{{ buttonClassName}}" href="{{ include.button_url }}">{{ include.button_lable }}</a>
+            {% if item.button_url && item.button_label  %}
+            <a class="{{ buttonClassName}}" href="{{ include.button_url }}">{{ include.button_label }}</a>
             {% endif %}
         </div>
       </div>
@@ -46,8 +46,8 @@ <h2>{{ include.title }}</h2>
             {% else %}
               {% assign buttonClassName = "button" %}
             {% endif %}
-            {% if item.button_url && item.button_lable  %}
-            <a class="{{ buttonClassName}}" href="{{ include.button_url }}">{{ include.button_lable }}</a>
+            {% if item.button_url && item.button_label  %}
+            <a class="{{ buttonClassName}}" href="{{ include.button_url }}">{{ include.button_label }}</a>
             {% endif %}
         </div>
       </div>
diff --git a/_includes/block_text.html b/_includes/block_text.html
index f63bdc1..ddc1236 100644
--- a/_includes/block_text.html
+++ b/_includes/block_text.html
@@ -15,7 +15,7 @@
           <img class="section-intro-img" src="{{ include.image }}" alt="" style="width:{{ include.image_size }}">
         {%- endif -%}
         <h2>{{ include.title }}</h2>
-        <p class="text-{{ include.paragraph_aligh }}">{{ include.paragraph }}</p>
+        <p class="text-{{ include.paragraph_align }}">{{ include.paragraph }}</p>
       </div>
     </div>
   </section>
\ No newline at end of file
diff --git a/_includes/block_text_cards.html b/_includes/block_text_cards.html
index e4e1c1d..e10fe38 100644
--- a/_includes/block_text_cards.html
+++ b/_includes/block_text_cards.html
@@ -25,9 +25,9 @@ <h2 style="height: 80px">{{ item.title }}</h2>
             {% else %}
               {% assign buttonClassName = "button" %}
             {% endif %}
-            {% if item.button_url && item.button_lable  %}
+            {% if item.button_url && item.button_label  %}
             <a class="{{ buttonClassName}}"
-                href="{{ item.button_url }}">{{ item.button_lable }}</a>
+                href="{{ item.button_url }}">{{ item.button_label }}</a>
             {% endif %}
         </div>
         {% endfor %}
diff --git a/_includes/block_text_image.html b/_includes/block_text_image.html
index 067ab47..d23f502 100644
--- a/_includes/block_text_image.html
+++ b/_includes/block_text_image.html
@@ -17,8 +17,8 @@ <h2>{{ include.title }}</h2>
             {% else %}
               {% assign buttonClassName = "button" %}
             {% endif %}
-            {% if item.button_url && item.button_lable  %}
-            <a class="{{ buttonClassName}}" href="{{ include.button_url }}">{{ include.button_lable }}</a>
+            {% if item.button_url && item.button_label  %}
+            <a class="{{ buttonClassName}}" href="{{ include.button_url }}">{{ include.button_label }}</a>
             {% endif %}
         </div>
         <div class="col-lg-6 col-md-6 mb-4 mb-md-0 ">
@@ -43,8 +43,8 @@ <h2>{{ include.title }}</h2>
             {% else %}
               {% assign buttonClassName = "button" %}
             {% endif %}
-            {% if item.button_url && item.button_lable  %}
-            <a class="{{ buttonClassName}}" href="{{ include.button_url }}">{{ include.button_lable }}</a>
+            {% if item.button_url && item.button_label  %}
+            <a class="{{ buttonClassName}}" href="{{ include.button_url }}">{{ include.button_label }}</a>
             {% endif %}
         </div>
         <div class="col-lg-6 col-md-6 mb-4 mb-md-0">
diff --git a/index.markdown b/index.markdown
index 8687acc..dffe0f2 100644
--- a/index.markdown
+++ b/index.markdown
@@ -17,20 +17,20 @@ blocks:
     title: Accomplish your company’s goals
     paragraph: Are you looking for a specifications factory that continually strives to optimize the delicate balance between the need for consensus and time to market through tools and simplified procedures, while empowering the people doing the work to complete a work item in the minimal amount of time. Markdown at [jekyllrb.com](https://jekyllrb.com/)
     image: assets/images/home/photo_example2.png
-    button_lable: "Lean More"
+    button_label: "Lean More"
     button_url: "https://www.google.com/"
     button_style: "link" #display style as link | button(default)
   - layout: "block_image_text"
     title: Developers wanted
     paragraph: Standard Hub has more than 150 specifications defined at the Open Mobile Alliance, IOT Smart Objects created at the IPSO Alliance, and developer tools  and resources that facilitate the development of products based on LightweightM2M (LwM2M), the IoT industry’s protocol for device management.
     image: assets/images/home/photo_example1.png
-    button_lable: "See More"
+    button_label: "See More"
     button_url: ""
     # button_style: "link" #display style as link | button(default)
   - layout: "block_text_fluid"
     title: Our Services
     paragraph: We have assembled a set of tools, a team, and procedures that are well-suited to a small group of companies with a common interest to spin up a simple effort that results in a pre-standards body of work, as well as a large scale, well-funded project with aspirations of creating a worldwide standard. <br/><br/>We can guide you through the consortium lifecycle from formation to the ongoing governance, the technical collaboration, and the finance and administration. We consider ourselves a part of your team with a singular focus on the execution of your mission.  We manage all the core business functions, so you can concentrate on delivering the best possible specifications for your industry.
-    paragraph_aligh: left # center | left
+    paragraph_align: left # center | left
     image: assets/images/home/section-icon.png
   - layout: "block_icon_cards"
     card_per_line: 3
@@ -38,44 +38,44 @@ blocks:
       - title: Formationsss
         paragraph: There are a number of ways to effectively start a new technical standards project. We will guide you to the path that best fits your needs.
         image: assets/images/home/service1.png
-        button_lable: "Lean More"
+        button_label: "Lean More"
         # button_url: ""
         align: center # center | left | right
       - title: Governance
         paragraph: Technical consortia must comply with the laws that govern non-profits and they should be governed neutrally for the benefit of all their stakeholders.
         image: assets/images/home/service2.png
-        button_lable: "Lean More"
+        button_label: "Lean More"
         button_url: ""
         button_style: "link" #display style as link | button(default)
       - title: Working Group Admin
         paragraph: We have helped consortium members create hundreds of specifications.  Every effort is unique, but they have some common features.
         image: assets/images/home/service3.png
-        button_lable: "Lean More"
+        button_label: "Lean More"
         button_url: ""
       - title: Membership Services
         paragraph: Now that you have settled on the mission, scope, and structure of your consortium, you need to connect with other stakeholders your industry.
         image: assets/images/home/service3.png
-        button_lable: "Lean More"
+        button_label: "Lean More"
         button_url: ""
       - title: Finance & Accounting
         paragraph: Consortia rely on the financial contributions of its members.  This requires invoicing, collections, and tax filings.
         image: assets/images/home/service3.png
-        button_lable: "Lean More"
+        button_label: "Lean More"
         button_url: ""
       - title: Events
         paragraph: Standards professionals are heavy travelers. The hallways of standards meetings often create some of the best breakthroughs.
         image: assets/images/home/service3.png
-        button_lable: "Lean More"
+        button_label: "Lean More"
         button_url: ""
       - title: Lifecycle Management
         paragraph: Most technical consortia are formed for a specific purpose.  But over time, their mission changes and may be considered complete.
         image: assets/images/home/service3.png
-        button_lable: "Lean More"
+        button_label: "Lean More"
         button_url: ""
       - title: Marketing & PR
         paragraph: Our marketing team can support consortia serving specific needs for a small group, as well as those tackling big issues with complex components.
         image: assets/images/home/service3.png
-        button_lable: "Lean More"
+        button_label: "Lean More"
         button_url: ""
   - layout: "block_text_cards"
     card_per_line: 4
@@ -84,50 +84,50 @@ blocks:
         paragraph: There are a number of ways to effectively start a new technical standards project. We will guide you to the path that best fits your needs.
         image: assets/images/home/section-icon.png
         image_align: right # left|center|right
-        button_lable: "Lean More"
+        button_label: "Lean More"
         button_url: ""
         button_style: "link"
       - title: Governance
         paragraph: Technical consortia must comply with the laws that govern non-profits and they should be governed neutrally for the benefit of all their stakeholders.
         image: assets/images/home/section-icon.png
         image_align: right  # left|center|right
-        button_lable: "Lean More"
+        button_label: "Lean More"
         button_url: ""
       - title: Working Group Admin
         paragraph: We have helped consortium members create hundreds of specifications.  Every effort is unique, but they have some common features.
         image: assets/images/home/section-icon.png
         image_align: right  # left|center|right
-        button_lable: "Lean More"
+        button_label: "Lean More"
         button_url: ""
       - title: Membership Services
         paragraph: Now that you have settled on the mission, scope, and structure of your consortium, you need to connect with other stakeholders your industry.
         image: assets/images/home/section-icon.png
         image_align: right  # left|center|right
-        button_lable: "Lean More"
+        button_label: "Lean More"
         button_url: ""
       - title: Finance & Accounting
         paragraph: Consortia rely on the financial contributions of its members.  This requires invoicing, collections, and tax filings.
         image: assets/images/home/section-icon.png
         image_align: right  # left|center|right
-        button_lable: "Lean More"
+        button_label: "Lean More"
         button_url: ""
       - title: Events
         paragraph: Standards professionals are heavy travelers. The hallways of standards meetings often create some of the best breakthroughs.
         image: assets/images/home/section-icon.png
         image_align: right  # left|center|right
-        button_lable: "Lean More"
+        button_label: "Lean More"
         button_url: ""
       - title: Lifecycle Management
         paragraph: Most technical consortia are formed for a specific purpose.  But over time, their mission changes and may be considered complete.
         image: assets/images/home/section-icon.png
         image_align: right  # left|center|right
-        button_lable: "Lean More"
+        button_label: "Lean More"
         button_url: ""
       - title: Marketing & PR
         paragraph: Our marketing team can support consortia serving specific needs for a small group, as well as those tackling big issues with complex components.
         image: assets/images/home/section-icon.png
         image_align: right 
-        button_lable: "Lean More"
+        button_label: "Lean More"
         button_url: ""
   - layout: "block_text_cards"
     card_per_line: 4
@@ -136,49 +136,49 @@ blocks:
         paragraph: There are a number of ways to effectively start a new technical standards project. We will guide you to the path that best fits your needs.
         image: assets/images/home/section-icon.png
         image_align: left # left|center|right
-        button_lable: "Lean More"
+        button_label: "Lean More"
         button_url: ""
       - title: Governance
         paragraph: Technical consortia must comply with the laws that govern non-profits and they should be governed neutrally for the benefit of all their stakeholders.
         image: assets/images/home/section-icon.png
         image_align: left  # left|center|right
-        button_lable: "Lean More"
+        button_label: "Lean More"
         button_url: ""
       - title: Group Admin
         paragraph: We have helped consortium members create hundreds of specifications.  Every effort is unique, but they have some common features.
         image: assets/images/home/section-icon.png
         image_align: left  # left|center|right
-        button_lable: "Lean More"
+        button_label: "Lean More"
         button_url: ""
       - title: Membership
         paragraph: Now that you have settled on the mission, scope, and structure of your consortium, you need to connect with other stakeholders your industry.
         image: assets/images/home/section-icon.png
         image_align: left  # left|center|right
-        button_lable: "Lean More"
+        button_label: "Lean More"
         button_url: ""
       - title: F & A
         paragraph: Consortia rely on the financial contributions of its members.  This requires invoicing, collections, and tax filings.
         image: assets/images/home/section-icon.png
         image_align: left  # left|center|right
-        button_lable: "Lean More"
+        button_label: "Lean More"
         button_url: ""
       - title: Events
         paragraph: Standards professionals are heavy travelers. The hallways of standards meetings often create some of the best breakthroughs.
         image: assets/images/home/section-icon.png
         image_align: left  # left|center|right
-        button_lable: "Lean More"
+        button_label: "Lean More"
         button_url: ""
       - title: Tech Lifecycle
         paragraph: Most technical consortia are formed for a specific purpose.  But over time, their mission changes and may be considered complete.
         image: assets/images/home/section-icon.png
         image_align: left  # left|center|right
-        button_lable: "Lean More"
+        button_label: "Lean More"
         button_url: ""
       - title: Marketing & PR
         paragraph: Our marketing team can support consortia serving specific needs for a small group, as well as those tackling big issues with complex components.
         image: assets/images/home/section-icon.png
         image_align: left 
-        button_lable: "Lean More"
+        button_label: "Lean More"
         button_url: ""
   - layout: "block_image_cards"
     header:
@@ -190,18 +190,18 @@ blocks:
       - title: Communications
         paragraph: The COM Working Group is responsible for service layer standardization of communications related technologies, including areas such as Messaging, Push-to-talk over Cellular, Presence, Contact Information and Spam Reporting.
         image: assets/images/gallery/g1.png
-        button_lable: "Lean More"
+        button_label: "Lean More"
         button_url: ""
         button_style: "link" #display style as link | button(default)
       - title: Content Delivery
         paragraph: The CD Working Group is chartered to define the basic delivery mechanisms, bi-directional exchange mechanisms, and the processing of key content formats, including the semantics and user agents, behavior and programming interfaces.
         image: assets/images/gallery/g2.png
-        button_lable: "Lean More"
+        button_label: "Lean More"
         button_url: ""
       - title: Interoperability
         paragraph: The IOP Working Group produces high quality test specifications, facilitating testing of implementations of OMA SpecWorks specifications and, in some cases, producing TTCN test code for the validation of specifications.
         image: assets/images/gallery/g3.png
-        button_lable: "Lean More"
+        button_label: "Lean More"
         button_url: ""
   - layout: "block_image_cards"
     card_per_line: 4
@@ -209,17 +209,17 @@ blocks:
       - title: Communications
         paragraph: The COM Working Group is responsible for service layer standardization of communications related technologies, including areas such as Messaging, Push-to-talk over Cellular, Presence, Contact Information and Spam Reporting.
         image: assets/images/gallery/g1.png
-        button_lable: "Lean More"
+        button_label: "Lean More"
         button_url: ""
         button_style: "link" #display style as link | button(default)
       - title: Content Delivery
         paragraph: The CD Working Group is chartered to define the basic delivery mechanisms, bi-directional exchange mechanisms, and the processing of key content formats, including the semantics and user agents, behavior and programming interfaces.
         image: assets/images/gallery/g2.png
-        button_lable: "Lean More"
+        button_label: "Lean More"
         button_url: ""
       - title: Interoperability
         paragraph: The IOP Working Group produces high quality test specifications, facilitating testing of implementations of OMA SpecWorks specifications and, in some cases, producing TTCN test code for the validation of specifications.
         image: assets/images/gallery/g3.png
-        button_lable: "Lean More"
+        button_label: "Lean More"
         button_url: ""
 ---