kafka-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jun...@apache.org
Subject kafka-site git commit: Add Apache trademark to first occurrence of Kafka in each page
Date Wed, 26 Oct 2016 23:43:26 GMT
Repository: kafka-site
Updated Branches:
  refs/heads/asf-site dfe3f3b57 -> c0f927fae


Add Apache trademark to first occurrence of Kafka in each page


Project: http://git-wip-us.apache.org/repos/asf/kafka-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/kafka-site/commit/c0f927fa
Tree: http://git-wip-us.apache.org/repos/asf/kafka-site/tree/c0f927fa
Diff: http://git-wip-us.apache.org/repos/asf/kafka-site/diff/c0f927fa

Branch: refs/heads/asf-site
Commit: c0f927fae6c08bc63872de5dbf674b3c6f897edf
Parents: dfe3f3b
Author: Derrick Or <derrickor@gmail.com>
Authored: Wed Oct 26 16:42:40 2016 -0700
Committer: Jun Rao <junrao@gmail.com>
Committed: Wed Oct 26 16:42:40 2016 -0700

----------------------------------------------------------------------
 0100/introduction.html |  2 +-
 0101/introduction.html |  2 +-
 0101/quickstart.html   |  2 +-
 0101/uses.html         |  2 +-
 08/introduction.html   | 12 +++++-------
 081/introduction.html  | 12 +++++-------
 082/introduction.html  | 12 +++++-------
 090/introduction.html  |  8 +++-----
 coding-guide.html      |  2 +-
 committers.html        |  2 +-
 contact.html           |  2 +-
 contributing.html      |  2 +-
 includes/_footer.htm   |  5 +++--
 index.html             |  2 +-
 performance.html       |  4 ++--
 project-security.html  |  2 +-
 project.html           |  2 +-
 styles.css             | 12 ++++++++----
 18 files changed, 42 insertions(+), 45 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/kafka-site/blob/c0f927fa/0100/introduction.html
----------------------------------------------------------------------
diff --git a/0100/introduction.html b/0100/introduction.html
index 09df9f6..f88a841 100644
--- a/0100/introduction.html
+++ b/0100/introduction.html
@@ -14,7 +14,7 @@
  See the License for the specific language governing permissions and
  limitations under the License.
 -->
-<h3>Kafka is <i>a distributed streaming platform</i>. What exactly does
that mean?</h3>
+<h3>Kafka&trade; is <i>a distributed streaming platform</i>. What exactly
does that mean?</h3>
 <p>We think of a streaming platform as having three key capabilities:</p>
 <ol>
 	<li>It let's you publish and subscribe to streams of records. In this respect it is
similar to a message queue or enterprise messaging system.

http://git-wip-us.apache.org/repos/asf/kafka-site/blob/c0f927fa/0101/introduction.html
----------------------------------------------------------------------
diff --git a/0101/introduction.html b/0101/introduction.html
index d034683..c9ab696 100644
--- a/0101/introduction.html
+++ b/0101/introduction.html
@@ -14,7 +14,7 @@
  See the License for the specific language governing permissions and
  limitations under the License.
 -->
-<h3> Kafka is <i>a distributed streaming platform</i>. What exactly does
that mean?</h3>
+<h3>Kafka&trade; is <i>a distributed streaming platform</i>. What exactly
does that mean?</h3>
 <p>We think of a streaming platform as having three key capabilities:</p>
 <ol>
 	<li>It lets you publish and subscribe to streams of records. In this respect it is
similar to a message queue or enterprise messaging system.

http://git-wip-us.apache.org/repos/asf/kafka-site/blob/c0f927fa/0101/quickstart.html
----------------------------------------------------------------------
diff --git a/0101/quickstart.html b/0101/quickstart.html
index 2e83cbb..f31cfb6 100644
--- a/0101/quickstart.html
+++ b/0101/quickstart.html
@@ -16,7 +16,7 @@
 -->
 
 <p>
-This tutorial assumes you are starting fresh and have no existing Kafka or ZooKeeper data.
+This tutorial assumes you are starting fresh and have no existing Kafka&trade; or ZooKeeper
data.
 Since Kafka console scripts are different for Unix-based and Windows platforms, on Windows
platforms use <code>bin\windows\</code> instead of <code>bin/</code>,
and change the script extension to <code>.bat</code>.
 </p>
 

http://git-wip-us.apache.org/repos/asf/kafka-site/blob/c0f927fa/0101/uses.html
----------------------------------------------------------------------
diff --git a/0101/uses.html b/0101/uses.html
index b86d917..2d238c2 100644
--- a/0101/uses.html
+++ b/0101/uses.html
@@ -15,7 +15,7 @@
  limitations under the License.
 -->
 
-<p> Here is a description of a few of the popular use cases for Apache Kafka. For an
overview of a number of these areas in action, see <a href="http://engineering.linkedin.com/distributed-systems/log-what-every-software-engineer-should-know-about-real-time-datas-unifying">this
blog post</a>. </p>
+<p> Here is a description of a few of the popular use cases for Apache Kafka&trade;.
For an overview of a number of these areas in action, see <a href="http://engineering.linkedin.com/distributed-systems/log-what-every-software-engineer-should-know-about-real-time-datas-unifying">this
blog post</a>. </p>
 
 <h4><a id="uses_messaging" href="#uses_messaging">Messaging</a></h4>
 

http://git-wip-us.apache.org/repos/asf/kafka-site/blob/c0f927fa/08/introduction.html
----------------------------------------------------------------------
diff --git a/08/introduction.html b/08/introduction.html
index 485ce8b..40879c0 100644
--- a/08/introduction.html
+++ b/08/introduction.html
@@ -1,9 +1,7 @@
 <h3><a id="introduction">1.1 Introduction</a></h3>
-Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality
of a messaging system, but with a unique design.
-<p>
-What does all that mean?
-<p>
-First let's review some basic messaging terminology:
+<p>Kafka&trade; is a distributed, partitioned, replicated commit log service. It
provides the functionality of a messaging system, but with a unique design.</p>
+<p>What does all that mean?</p>
+<p>First let's review some basic messaging terminology:</p>
 <ul>
 	<li>Kafka maintains feeds of messages in categories called <i>topics</i>.
 	<li>We'll call processes that publish messages to a Kafka topic <i>producers</i>.
@@ -33,7 +31,7 @@ In fact the only metadata retained on a per-consumer basis is the position
of th
 <p>
 This combination of features means that Kafka consumers are very cheap&mdash;they can
come and go without much impact on the cluster or on other consumers. For example, you can
use our command line tools to "tail" the contents of any topic without changing what is consumed
by any existing consumers.
 <p>
-The partitions in the log serve several purposes. First, they allow the log to scale beyond
a size that will fit on a single server. Each individual partition must fit on the servers
that host it, but a topic may have many partitions so it can handle an arbitrary amount of
data. Second they act as the unit of parallelism&mdash;more on that in a bit. 
+The partitions in the log serve several purposes. First, they allow the log to scale beyond
a size that will fit on a single server. Each individual partition must fit on the servers
that host it, but a topic may have many partitions so it can handle an arbitrary amount of
data. Second they act as the unit of parallelism&mdash;more on that in a bit.
 
 <h4>Distribution</h4>
 
@@ -53,7 +51,7 @@ Consumers label themselves with a consumer group name, and each message
publishe
 <p>
 If all the consumer instances have the same consumer group, then this works just like a traditional
queue balancing load over the consumers.
 <p>
-If all the consumer instances have different consumer groups, then this works like publish-subscribe
and all messages are broadcast to all consumers. 
+If all the consumer instances have different consumer groups, then this works like publish-subscribe
and all messages are broadcast to all consumers.
 <p>
 More commonly, however, we have found that topics have a small number of consumer groups,
one for each "logical subscriber". Each group is composed of many consumer instances for scalability
and fault tolerance. This is nothing more than publish-subscribe semantics where the subscriber
is cluster of consumers instead of a single process.
 <p>

http://git-wip-us.apache.org/repos/asf/kafka-site/blob/c0f927fa/081/introduction.html
----------------------------------------------------------------------
diff --git a/081/introduction.html b/081/introduction.html
index f82750d..73b13ae 100644
--- a/081/introduction.html
+++ b/081/introduction.html
@@ -1,9 +1,7 @@
 <h3><a id="introduction">1.1 Introduction</a></h3>
-Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality
of a messaging system, but with a unique design.
-<p>
-What does all that mean?
-<p>
-First let's review some basic messaging terminology:
+<p>Kafka&trade; is a distributed, partitioned, replicated commit log service. It
provides the functionality of a messaging system, but with a unique design.</p>
+<p>What does all that mean?</p>
+<p>First let's review some basic messaging terminology:</p>
 <ul>
     <li>Kafka maintains feeds of messages in categories called <i>topics</i>.
     <li>We'll call processes that publish messages to a Kafka topic <i>producers</i>.
@@ -33,7 +31,7 @@ In fact the only metadata retained on a per-consumer basis is the position
of th
 <p>
 This combination of features means that Kafka consumers are very cheap&mdash;they can
come and go without much impact on the cluster or on other consumers. For example, you can
use our command line tools to "tail" the contents of any topic without changing what is consumed
by any existing consumers.
 <p>
-The partitions in the log serve several purposes. First, they allow the log to scale beyond
a size that will fit on a single server. Each individual partition must fit on the servers
that host it, but a topic may have many partitions so it can handle an arbitrary amount of
data. Second they act as the unit of parallelism&mdash;more on that in a bit. 
+The partitions in the log serve several purposes. First, they allow the log to scale beyond
a size that will fit on a single server. Each individual partition must fit on the servers
that host it, but a topic may have many partitions so it can handle an arbitrary amount of
data. Second they act as the unit of parallelism&mdash;more on that in a bit.
 
 <h4>Distribution</h4>
 
@@ -53,7 +51,7 @@ Consumers label themselves with a consumer group name, and each message
publishe
 <p>
 If all the consumer instances have the same consumer group, then this works just like a traditional
queue balancing load over the consumers.
 <p>
-If all the consumer instances have different consumer groups, then this works like publish-subscribe
and all messages are broadcast to all consumers. 
+If all the consumer instances have different consumer groups, then this works like publish-subscribe
and all messages are broadcast to all consumers.
 <p>
 More commonly, however, we have found that topics have a small number of consumer groups,
one for each "logical subscriber". Each group is composed of many consumer instances for scalability
and fault tolerance. This is nothing more than publish-subscribe semantics where the subscriber
is cluster of consumers instead of a single process.
 <p>

http://git-wip-us.apache.org/repos/asf/kafka-site/blob/c0f927fa/082/introduction.html
----------------------------------------------------------------------
diff --git a/082/introduction.html b/082/introduction.html
index f82750d..73b13ae 100644
--- a/082/introduction.html
+++ b/082/introduction.html
@@ -1,9 +1,7 @@
 <h3><a id="introduction">1.1 Introduction</a></h3>
-Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality
of a messaging system, but with a unique design.
-<p>
-What does all that mean?
-<p>
-First let's review some basic messaging terminology:
+<p>Kafka&trade; is a distributed, partitioned, replicated commit log service. It
provides the functionality of a messaging system, but with a unique design.</p>
+<p>What does all that mean?</p>
+<p>First let's review some basic messaging terminology:</p>
 <ul>
     <li>Kafka maintains feeds of messages in categories called <i>topics</i>.
     <li>We'll call processes that publish messages to a Kafka topic <i>producers</i>.
@@ -33,7 +31,7 @@ In fact the only metadata retained on a per-consumer basis is the position
of th
 <p>
 This combination of features means that Kafka consumers are very cheap&mdash;they can
come and go without much impact on the cluster or on other consumers. For example, you can
use our command line tools to "tail" the contents of any topic without changing what is consumed
by any existing consumers.
 <p>
-The partitions in the log serve several purposes. First, they allow the log to scale beyond
a size that will fit on a single server. Each individual partition must fit on the servers
that host it, but a topic may have many partitions so it can handle an arbitrary amount of
data. Second they act as the unit of parallelism&mdash;more on that in a bit. 
+The partitions in the log serve several purposes. First, they allow the log to scale beyond
a size that will fit on a single server. Each individual partition must fit on the servers
that host it, but a topic may have many partitions so it can handle an arbitrary amount of
data. Second they act as the unit of parallelism&mdash;more on that in a bit.
 
 <h4>Distribution</h4>
 
@@ -53,7 +51,7 @@ Consumers label themselves with a consumer group name, and each message
publishe
 <p>
 If all the consumer instances have the same consumer group, then this works just like a traditional
queue balancing load over the consumers.
 <p>
-If all the consumer instances have different consumer groups, then this works like publish-subscribe
and all messages are broadcast to all consumers. 
+If all the consumer instances have different consumer groups, then this works like publish-subscribe
and all messages are broadcast to all consumers.
 <p>
 More commonly, however, we have found that topics have a small number of consumer groups,
one for each "logical subscriber". Each group is composed of many consumer instances for scalability
and fault tolerance. This is nothing more than publish-subscribe semantics where the subscriber
is cluster of consumers instead of a single process.
 <p>

http://git-wip-us.apache.org/repos/asf/kafka-site/blob/c0f927fa/090/introduction.html
----------------------------------------------------------------------
diff --git a/090/introduction.html b/090/introduction.html
index e5b2e78..8439efb 100644
--- a/090/introduction.html
+++ b/090/introduction.html
@@ -16,11 +16,9 @@
 -->
 
 <h3><a id="introduction" href="#introduction">1.1 Introduction</a></h3>
-Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality
of a messaging system, but with a unique design.
-<p>
-What does all that mean?
-<p>
-First let's review some basic messaging terminology:
+<p>Kafka&trade; is a distributed, partitioned, replicated commit log service. It
provides the functionality of a messaging system, but with a unique design.</p>
+<p>What does all that mean?</p>
+<p>First let's review some basic messaging terminology:</p>
 <ul>
     <li>Kafka maintains feeds of messages in categories called <i>topics</i>.
     <li>We'll call processes that publish messages to a Kafka topic <i>producers</i>.

http://git-wip-us.apache.org/repos/asf/kafka-site/blob/c0f927fa/coding-guide.html
----------------------------------------------------------------------
diff --git a/coding-guide.html b/coding-guide.html
index bfdacc7..887fed5 100644
--- a/coding-guide.html
+++ b/coding-guide.html
@@ -5,7 +5,7 @@
 	<div class="right">
 		<h1>Coding guidelines</h1>
 		<p>
-		These guidelines are meant to encourage consistency and best practices amongst people working
on the Kafka code base. They should be observed unless there is a compelling reason to ignore
them.
+		These guidelines are meant to encourage consistency and best practices amongst people working
on the Kafka&trade; code base. They should be observed unless there is a compelling reason
to ignore them.
 		</p>
 
 		<h2>Basic Stuff</h2>

http://git-wip-us.apache.org/repos/asf/kafka-site/blob/c0f927fa/committers.html
----------------------------------------------------------------------
diff --git a/committers.html b/committers.html
index 4d6c392..6681eca 100644
--- a/committers.html
+++ b/committers.html
@@ -36,7 +36,7 @@
     	  <a href="https://twitter.com/allthingshadoop">@allthingshadoop</a>
         </td>
         <td>
-          <img src="images/jay.jpg" height="150">
+          <img src="images/jay.jpg" width="150">
         </td>
         <td>
     	  Jay Kreps<br>

http://git-wip-us.apache.org/repos/asf/kafka-site/blob/c0f927fa/contact.html
----------------------------------------------------------------------
diff --git a/contact.html b/contact.html
index 94f0c3a..4045971 100644
--- a/contact.html
+++ b/contact.html
@@ -11,7 +11,7 @@
 		</p>
 		<ul>
 			<li>
-			  <a href="mailto: users@kafka.apache.org">users@kafka.apache.org</a>: A list
for general user questions about Kafka. To subscribe, send an email to <a href="mailto:
users-subscribe@kafka.apache.org">users-subscribe@kafka.apache.org</a>. Archives
are available <a href="http://mail-archives.apache.org/mod_mbox/kafka-users">here</a>.
+			  <a href="mailto: users@kafka.apache.org">users@kafka.apache.org</a>: A list
for general user questions about Kafka&trade;. To subscribe, send an email to <a href="mailto:
users-subscribe@kafka.apache.org">users-subscribe@kafka.apache.org</a>. Archives
are available <a href="http://mail-archives.apache.org/mod_mbox/kafka-users">here</a>.
 			</li>
 			<li>
 			  <a href="mailto: dev@kafka.apache.org">dev@kafka.apache.org</a>: A list
for discussion on Kafka development. To subscribe, send an email to <a href="mailto: dev-subscribe@kafka.apache.org">dev-subscribe@kafka.apache.org</a>.
Archives available <a href="http://mail-archives.apache.org/mod_mbox/kafka-dev">here</a>.

http://git-wip-us.apache.org/repos/asf/kafka-site/blob/c0f927fa/contributing.html
----------------------------------------------------------------------
diff --git a/contributing.html b/contributing.html
index a77fca3..f78f1e1 100644
--- a/contributing.html
+++ b/contributing.html
@@ -6,7 +6,7 @@
 		<h1>How to contribute</h1>
 		<p>We are always very happy to have contributions, whether for trivial cleanups or
big new features.</p>
 		<p>
-		If you don't know Java or Scala you can still contribute to the project. An important area
is the <a href="https://cwiki.apache.org/confluence/display/KAFKA/Clients">clients</a>.
We want to have high quality, well documented clients for each programming language. These,
as well as the surrounding <a href="https://cwiki.apache.org/confluence/display/KAFKA/Ecosystem">ecosystem</a>
of integration tools that people use with Kafka, are critical aspects of the project.
+		If you don't know Java or Scala you can still contribute to the project. An important area
is the <a href="https://cwiki.apache.org/confluence/display/KAFKA/Clients">clients</a>.
We want to have high quality, well documented clients for each programming language. These,
as well as the surrounding <a href="https://cwiki.apache.org/confluence/display/KAFKA/Ecosystem">ecosystem</a>
of integration tools that people use with Kafka&trade;, are critical aspects of the project.
 		<p>
 		Nor is code the only way to contribute to the project. We strongly value documentation
and gladly accept improvements to the documentation.
 

http://git-wip-us.apache.org/repos/asf/kafka-site/blob/c0f927fa/includes/_footer.htm
----------------------------------------------------------------------
diff --git a/includes/_footer.htm b/includes/_footer.htm
index 793ddb8..a104f23 100644
--- a/includes/_footer.htm
+++ b/includes/_footer.htm
@@ -4,8 +4,9 @@
 		<div class="footer">
 			<div class="footer__inner">
 				<div class="footer__legal">
-					<span>The contents of this website are &copy; 2016 <a href="https://www.apache.org/"
target="_blank">Apache Software Foundation</a> under the terms of the <a href="https://www.apache.org/licenses/LICENSE-2.0.html"
target="_blank">Apache License v2</a>.</span>
-					<span>Apache Kafka and its logo are trademarks of the Apache Software Foundation.</span>
+					<span class="footer__legal__one">The contents of this website are &copy; 2016
<a href="https://www.apache.org/" target="_blank">Apache Software Foundation</a>
under the terms of the <a href="https://www.apache.org/licenses/LICENSE-2.0.html" target="_blank">Apache
License v2</a>.</span>
+					<span class="footer__legal__two">Apache Kafka, Kafka, and the Kafka logo are either
registered trademarks or trademarks of The Apache Software Foundation</span>
+					<span class="footer__legal__three">in the United States and other countries.</span>
 				</div>
 				<a class="apache-feather" target="_blank" href="http://www.apache.org">
 					<img width="40" src="/images/feather-small.png" alt="Apache Feather">

http://git-wip-us.apache.org/repos/asf/kafka-site/blob/c0f927fa/index.html
----------------------------------------------------------------------
diff --git a/index.html b/index.html
index 05fd198..38b886b 100644
--- a/index.html
+++ b/index.html
@@ -20,7 +20,7 @@
 		<div class="index">
 			<img width="451" height="435" class="kafka-diagram" src="/images/kafka_diagram.png">
 			<div class="callout">
-				<p>Kafka is used for building real-time data pipelines and streaming apps. It is
horizontally scalable, fault-tolerant, wicked fast, and runs in production in thousands of
companies.</p>
+				<p>Kafka&trade; is used for building real-time data pipelines and streaming
apps. It is horizontally scalable, fault-tolerant, wicked fast, and runs in production in
thousands of companies.</p>
 				<a class="btn btn--secondary btn--sm callout__action" href="/intro.html">Learn
more</a>
 			</div>
 		</div>

http://git-wip-us.apache.org/repos/asf/kafka-site/blob/c0f927fa/performance.html
----------------------------------------------------------------------
diff --git a/performance.html b/performance.html
index d060936..07c5c7a 100644
--- a/performance.html
+++ b/performance.html
@@ -4,8 +4,8 @@
 	<!--#include virtual="includes/_nav.htm" -->
 	<div class="right">
 		<h1>Performance</h1>
-    <p>A brief overview of the performance characteristics of Kafka.</p>
-		<a href="http://engineering.linkedin.com/kafka/benchmarking-apache-kafka-2-million-writes-second-three-cheap-machines">Read
blog post</a> 
+    <p>A brief overview of the performance characteristics of Kafka&trade;.</p>
+		<a href="http://engineering.linkedin.com/kafka/benchmarking-apache-kafka-2-million-writes-second-three-cheap-machines">Read
blog post</a>
 
 <!--#include virtual="includes/_footer.htm" -->
 

http://git-wip-us.apache.org/repos/asf/kafka-site/blob/c0f927fa/project-security.html
----------------------------------------------------------------------
diff --git a/project-security.html b/project-security.html
index 85a6eb5..5e663a8 100644
--- a/project-security.html
+++ b/project-security.html
@@ -22,7 +22,7 @@
 	<div class="right">
 		<h1>Kafka security</h1>
 		<p>
-			The Apache Software Foundation takes security issues very seriously. Apache Kafka specifically
offers security features and is responsive to issues around its features. If you have any
concern around Kafka Security or believe you have uncovered a vulnerability, we suggest that
you get in touch via the e-mail address <a href="mailto:security@kafka.apache.org?Subject=[SECURITY]
My security issue" target="_top">security@kafka.apache.org</a>. In the message, try
to provide a description of the issue and ideally a way of reproducing it. The security team
will get back to you after assessing the description.
+			The Apache Software Foundation takes security issues very seriously. Apache Kafka&trade;
specifically offers security features and is responsive to issues around its features. If
you have any concern around Kafka Security or believe you have uncovered a vulnerability,
we suggest that you get in touch via the e-mail address <a href="mailto:security@kafka.apache.org?Subject=[SECURITY]
My security issue" target="_top">security@kafka.apache.org</a>. In the message, try
to provide a description of the issue and ideally a way of reproducing it. The security team
will get back to you after assessing the description.
 		</p>
 		<p>
 			Note that this security address should be used only for undisclosed vulnerabilities. Dealing
with fixed issues or general questions on how to use the security features should be handled
regularly via the user and the dev lists. <b>Please report any security problems to
the project security address before disclosing it publicly.</b>

http://git-wip-us.apache.org/repos/asf/kafka-site/blob/c0f927fa/project.html
----------------------------------------------------------------------
diff --git a/project.html b/project.html
index 82c41db..e149f7d 100644
--- a/project.html
+++ b/project.html
@@ -28,7 +28,7 @@
 		<h3 class="bullet">Committers</h3>
 		<a class="pb-10" href="/committers">See the project committers</a>
 		<h3 class="bullet">Security</h3>
-		<a class="pb-10" href="/project-security">Learn about Kafka security</a>
+		<a class="pb-10" href="/project-security">Learn about Kafka&trade; security</a>
 		<h3 class="bullet">Papers &amp; talks</h3>
 		<a class="pb-10" href="https://cwiki.apache.org/confluence/display/KAFKA/Kafka+papers+and+presentations"
target="_blank">View our papers and talks</a>
 		<h3 class="bullet">Developer info</h3>

http://git-wip-us.apache.org/repos/asf/kafka-site/blob/c0f927fa/styles.css
----------------------------------------------------------------------
diff --git a/styles.css b/styles.css
index 17e0c96..6cfbd11 100644
--- a/styles.css
+++ b/styles.css
@@ -197,6 +197,7 @@ ul {
 	width: 100%;
 	border-top: .1rem solid #dedede;
 	font-size: .9rem;
+	line-height: 1.2rem;
 	color: #888888;
 	padding: 2rem 0;
 }
@@ -278,7 +279,7 @@ nav .btn {
 	margin-top: 4rem;
 }
 .social-links {
-	margin-top: 2rem;
+	margin: 2rem 0 3rem;
 	font-size: 1.2rem;
 }
 .twitter {
@@ -429,6 +430,9 @@ nav .btn {
 		max-width: 100%;
 		margin: 0 2rem;
 	}
+	.footer__legal__one {
+		display:block;
+	}
 }
 
 @media only screen and (max-width: 1035px) {
@@ -456,9 +460,6 @@ nav .btn {
 	.apache-feather {
 		bottom: 2.8rem;
 	}
-	.footer__legal span {
-		display:block;
-	}
 }
 
 @media only screen and (max-width: 800px) {
@@ -478,6 +479,9 @@ nav .btn {
 	.callout::before {
 		right: 25%;
 	}
+	.footer__legal__two {
+		display:block;
+	}
 }
 
 @media only screen and (max-width: 650px) {


Mime
View raw message